Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

test-agency-assignment-02npm

test-agency-assignment-02 is a confirmed malicious npm package (MAL-2026-17297) that executes malicious code on install (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-agency-assignment-02 (npm)

MAL-2026-17297
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-agency-assignment-02

What this malware does

The tarball contains only package.json and 4444.vbs; the declared main entry (index.js) is absent. package.json defines a postinstall script wscript.exe 4444.vbs, so on npm install on Windows the VBScript executes automatically. 4444.vbs is heavily obfuscated (colon-delimited XOR-encoded CreateObject strings, embedded AES S-box and ChaCha20-IETF routines, and 600+ base64 fragments reconstructed at runtime) and presents cover strings identifying itself as Device Telemetry Aggregator / Verdant Signals Corp.. It reconstructs an encrypted payload, writes it to %TEMP% as a pf*.dat file, and invokes powershell.exe to perform process hollowing of the decoded loader. The package ships no library code — its only reachable behavior is the install-time dropper.

Malicious versions

1 flagged
1.0.5

Indicators of compromise (SHA-256)

e9944ea8ca21c0670c4b718a12427e8ca7330571ef5a9198a60b05f75038fe73

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test-agency-assignment-02 (version 1.0.5). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-agency-assignment-02 across your stack and pipelines.

  2. If you installed it — respond

    Remove test-agency-assignment-02 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If test-agency-assignment-02 was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks test-agency-assignment-02 before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. test-agency-assignment-02 on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020692

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test-agency-assignment-02-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore