Which versions of rony-testing are malicious?

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

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

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

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

Yes — rony-testing is associated with the GHSA-7p38-gfgq-g3f3, IN-MAL-2026-008104 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 rony-testing 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 rony-testing (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 rony-testing across your stack and pipelines.

Malicious package

rony-testingnpm

rony-testing is a confirmed malicious npm package (MAL-2026-6968) 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 rony-testing (npm)

MAL-2026-6968

Immediate action

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

npm uninstall rony-testing

What this malware does

The package's postinstall hook auto-executes index.js on npm install. The script collects the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working directory, serializes them as JSON, and POSTs the payload to a hardcoded webhook.site endpoint (https://webhook.site/7088d897-5b86-4deb-8d29-5b7a263a49b4). Request errors are silently swallowed to avoid alerting the installer. There is no documented purpose, no consent prompt, and no configuration option — the beacon fires unconditionally on install and transmits installer identity to an attacker-controlled collector.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

dd22e28563599a42a6e24483bb8a95fab6f272be26b452ddb9d8eb4b8390b42a

be1a5728b472335e46d1df74becaf6355424f1f32d068bb517c079d88cacc03c

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 rony-testing (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 rony-testing across your stack and pipelines.
If you installed it — respond
rony-testing 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 rony-testing 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 rony-testing 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. rony-testing 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

GHSA-7p38-gfgq-g3f3IN-MAL-2026-008104

References

Credits

Amazon Inspector · finder

Detect & block this

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