Which versions of thunder-rony are malicious?

The following npm versions of thunder-rony are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate thunder-rony if I installed it?

thunder-rony 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 thunder-rony — how do I know if it already compromised me?

If thunder-rony 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 thunder-rony part of a known attack campaign?

Yes — thunder-rony is associated with the IN-MAL-2026-008105 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 thunder-rony across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for thunder-rony (version 99.9.9).

Malicious package

thunder-ronynpm

Advisory published Jul 8, 2026Updated Jul 8, 2026

thunder-rony is a confirmed malicious npm package (MAL-2026-7004) that steals credentials and exfiltrates sensitive data (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in thunder-rony (npm)

MAL-2026-7004

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall thunder-rony

What this malware does

On npm install, the package's postinstall hook executes index.js, which collects the installer's OS username (os.userInfo().username), hostname (os.hostname()), non-internal IPv4 address from os.networkInterfaces(), and the working directory (INIT_CWD / cwd), and POSTs them via https.request to a hardcoded webhook.site capture URL (https://webhook.site/742b2c61-b48c-4540-9963-a33713dedaf1). No functional code accompanies the beacon; package metadata is empty (description/author/keywords) and the version is an implausible 99.9.9, consistent with a dependency-confusion or reconnaissance-squat probe. Installing the package causes automatic, non-consensual exfiltration of installer identity and environment data to an attacker-controlled endpoint.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

b49da9c4d3522da30e4c917c3102444f9d61d3ab3e9c547b74b9240168754b9a

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for thunder-rony (version 99.9.9).
If you installed it — respond
thunder-rony 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 thunder-rony 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. thunder-rony on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008105

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks thunder-rony-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