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

test-npm-snurkeburk-hackeronenpm

test-npm-snurkeburk-hackerone is a confirmed malicious npm package (MAL-2026-14141) that steals credentials and exfiltrates sensitive data (malicious version 1.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-npm-snurkeburk-hackerone (npm)

MAL-2026-14141
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall test-npm-snurkeburk-hackerone

What this malware does

The package's preinstall lifecycle hook runs node index.js, which shells out to collect installer host identifiers (hostname, cwd, whoami) and the installer's public IP (via curl to ifconfig.me), hex-encodes the concatenated result, and issues nslookup queries against subdomains of snurkeburk.com. This exfiltrates installer host identity over DNS at npm install time, before any consumer code runs. There is no legitimate purpose for a package to encode host identifiers into DNS lookups against an author-controlled zone.

Malicious versions

1 flagged
1.999.0

Indicators of compromise (SHA-256)

0397c2435e4a2a4b33ec6cc8e396eacfa099aea042b3da6e70d96d86ea53a460

Detection & response playbook

Credential / info stealer

  1. Find it

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

  2. If you installed it — respond

    test-npm-snurkeburk-hackerone is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If test-npm-snurkeburk-hackerone 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-npm-snurkeburk-hackerone 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-npm-snurkeburk-hackerone on npm has been identified as a malicious package (version 1.999.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018195

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks test-npm-snurkeburk-hackerone-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
test-npm-snurkeburk-hackerone (npm) malicious package — MAL-2026-14141 | O3 Security