How a Malicious VSIX Uses the Signed Editor Runtime
How a fake Google Update Support extension installs its components and runs the editor's own Electron binary as a Node interpreter.

Series
Six parts from an artifact-led investigation of a fake-recruitment campaign that targeted software developers: a malicious VS Code extension, parse-only deobfuscation, a GitLab dead drop, target harvesting from commit metadata, detection engineering, and the boundary between a public framework and the collection tools. All fourteen parts and both papers are on the research site: https://krasforge.github.io/UNK_DeadDrop/

How a fake Google Update Support extension installs its components and runs the editor's own Electron binary as a Node interpreter.

Rebuilding an AES key from sixteen obfuscated fragments with Acorn, proven by authenticated decryption without running the extension.

How a GitLab-hosted configuration file let the UNK_DeadDrop operators change servers without new payloads, and what its revision history reveals.

Reconstructing the harvester, sender configuration and aggregate counts behind two SQLite targeting pools. Original URL

Thirty-three YARA rules replayed against retained artifacts, followed by a separate noise review and static scanner evaluation.

Overlord build metadata, browser-store selectors, wallet-upload markers and capture components in the Linux agent.
