UNK_DeadDrop technical series
The series starts with three recruitment messages received in June and July 2026. It follows the evidence through clipboard substitution, a malicious editor extension, credential and wallet collection, mutable infrastructure, targeting databases, administration software, and experimental detections.
The underlying case evidence ends on 24 July 2026. Public reporting was checked through 25 October 2026. Each article distinguishes static capability from observed execution and identifies where the retained artifacts stop.
Read the investigation
Section titled “Read the investigation”- Anatomy of a Developer Lure: ClickFix Clipboard Manipulation
- How a Malicious VSIX Uses the Signed Editor Runtime
- Parsing Without Executing: JavaScript Deobfuscation with Acorn
- Inside the Collector: Browser Credentials and Wallet Files
- Beyond Screenshot Strings: Reconstructing Screen Capture
- Following the GitLab Dead Drop
- From Commit Metadata to a Developer Target List
- Inside rms-platform
- Tracing the ECHOES Archive
- From Three Phishing Emails to a Connected Investigation
- Building and Testing Detections for UNK_DeadDrop
- Where Overlord Ends and the Collection Toolchain Begins
- What 2.8 Million Files Revealed About unk-scanner
- When a Decoder Returns the Wrong Strings
The published material excludes raw contact databases, credentials, and a complete forensic sample set. Supporting PDFs are edited evidence reports derived from the restricted case material. The series does not claim successful compromise, financial loss, or real-world attribution where the artifacts do not establish those outcomes.
About the author
Section titled “About the author”Ilja Krasnjanski is an independent security researcher publishing as KrasForge. He studies developer recruitment lures, malware and detection methods. More about the author.