Which versions of test-npm-snurkeburk-hackerone are malicious?

The following npm versions of test-npm-snurkeburk-hackerone are flagged malicious: 1.999.0. Treat any of these as compromised.

How do I remediate test-npm-snurkeburk-hackerone if I installed it?

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.

I already installed test-npm-snurkeburk-hackerone — how do I know if it already compromised me?

If 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.

Is test-npm-snurkeburk-hackerone part of a known attack campaign?

Yes — test-npm-snurkeburk-hackerone is associated with the IN-MAL-2026-018195 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find test-npm-snurkeburk-hackerone across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for test-npm-snurkeburk-hackerone (version 1.999.0).

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

Find it
Search your lockfiles and build artifacts for test-npm-snurkeburk-hackerone (version 1.999.0).
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.
Did it already run?
If 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. 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

npmjs.com

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