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

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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ronyfortest (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ronyfortest across your stack and pipelines.

Malicious package

ronyfortestnpm

Malicious code in ronyfortest (npm) Remove it immediately and rotate any exposed credentials.

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ronyfortest (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ronyfortest across your stack and pipelines.
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 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 ronyfortest 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

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