@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)
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sidp-kiosk/test-npm-snurkeburk-hackerone (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sidp-kiosk/test-npm-snurkeburk-hackerone across your stack and pipelines.
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.
Did it already run?
If @sidp-kiosk/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.
How O3 protects you
O3 blocks @sidp-kiosk/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
Campaign
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.