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

@sidp-kiosk/test-npm-snurkeburk-hackeronenpm

@sidp-kiosk/test-npm-snurkeburk-hackerone is a confirmed malicious npm package (MAL-2026-14161) that steals credentials and exfiltrates sensitive data (malicious versions 1.999.0, 2.999.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sidp-kiosk/test-npm-snurkeburk-hackerone (npm)

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

What this malware does

The package's package.json declares a preinstall script that runs index.js automatically on npm install. index.js shells out via child_process.exec to collect the installer's hostname, current working directory, username, a package marker, and the machine's public IP (fetched via curl to ifconfig.me). The aggregated output is hex-encoded with xxd and split into DNS labels queried via nslookup against subdomains of snurkeburk.com, a DNS-tunnel exfiltration channel that bypasses egress HTTP filtering. Installing this package causes host identifiers and public IP to leave the machine to an attacker-controlled DNS namespace.

Malicious versions

2 flagged
1.999.02.999.0

Indicators of compromise (SHA-256)

65e2ca95b5e61ad788c9aaa4d42446bb772cd5bbd71569ff8babafbeea75d2fa
69a832d2eb4042899a17a745bac70590844ba320f3e181580314687c664e5159

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @sidp-kiosk/test-npm-snurkeburk-hackerone (2 malicious versions).

  2. If you installed it — respond

    @sidp-kiosk/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 @sidp-kiosk/test-npm-snurkeburk-hackerone was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @sidp-kiosk/test-npm-snurkeburk-hackerone on npm has been identified as a malicious package (versions 1.999.0, 2.999.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018260IN-MAL-2026-018259

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @sidp-kiosk/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
@sidp-kiosk/test-npm-snurkeburk-hackerone (npm) malicious package — MAL-2026-14161 | O3 Security