malwareCoreRuns in the API, always on

Peel the Config

  • easy
  • 100 pts
  • First blood: still open

The specimen's settings are not stored in the open. They sit in a configuration blob that has been encoded twice, so a plain strings search shows only nonsense. Encoding is not encryption: it is a reversible change of representation that anyone can undo once they recognise it. Recognising it is the skill here.

Use the viewer's decoder bench. Look at the blob, decide what it resembles (the character set and the length are good clues) and apply one operation at a time. After each step, ask whether the result looks more like text or still looks like noise. When you have peeled both layers you will be able to read a small set of fields.

Everything here is an inert teaching specimen made by us in our own format: it contains no working code, and every host and address in it is fictional. The configuration is invented, and the decoder bench only transforms text in your browser.

Read the decoded fields and submit the command-and-control host the configuration names. Obfuscation like this is a signal in itself: something hid this on purpose.

  • malware-analysis
  • obfuscation
  • config-extraction

Hints

Hints do not affect your points. Each one stays revealed.

Hint 1
Hint 2
Hint 3
Jump to workbench
Loading the play area...