Which versions of ronyfortest are malicious?

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

How do I remediate ronyfortest if I installed it?

ronyfortest establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ronyfortest — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for ronyfortest (version 99.9.9).

Malicious package

ronyfortestnpm

Advisory published Jul 8, 2026Updated Jul 8, 2026

ronyfortest is a confirmed malicious npm package (MAL-2026-7002) that opens a backdoor for remote access (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ronyfortest (npm)

MAL-2026-7002

Immediate action

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

npm uninstall ronyfortest

What this malware does

The package's postinstall hook (node index.js) runs automatically on npm install and collects the installer's OS username (os.userInfo().username), hostname (os.hostname()), and working directory (process.env.INIT_CWD || process.cwd()), then POSTs them as JSON to a hardcoded webhook.site inspector URL (https://webhook.site/49781ccd-e409-4a90-8a42-34ed52b9e7b1). package.json ships empty author/description/keywords metadata and declares no legitimate purpose. The behavior is an unconditional install-time beacon that leaks installer host/user identifiers to an author-controlled inspection endpoint.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

8c9f63368f7e1147ade261a87f45e32e13bcf79b5336efad59087ce85e64a849

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for ronyfortest (version 99.9.9).
If you installed it — respond
ronyfortest establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ronyfortest 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. ronyfortest 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-008103

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ronyfortest-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database