Which versions of test1ro are malicious?

The following npm versions of test1ro are flagged malicious: 99.99.99, 999.99.99. Treat any of these as compromised.

How do I remediate test1ro if I installed it?

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

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

Yes — test1ro is associated with the IN-MAL-2026-020212, IN-MAL-2026-020210 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 test1ro 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 test1ro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test1ro across your stack and pipelines.

Malicious package

test1ronpm

test1ro is a confirmed malicious npm package (MAL-2026-16315) that opens a backdoor for remote access (malicious versions 99.99.99, 999.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test1ro (npm)

MAL-2026-16315

Immediate action

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

npm uninstall test1ro

What this malware does

package.json declares preinstall and postinstall hooks that run node index.js, which reads os.hostname() and issues an HTTP GET to the hardcoded third-party collector http://eo8f3m3ho26a0nm.m.pipedream.net/<package>?h=<hostname>. The behavior fires automatically during npm install without any user action, transmitting the installer's host identifier and the resolved package name to an external Pipedream request-bin. The manifest also declares test1ro: ^999.99.99 as its own dependency at an implausibly high version, characteristic of a dependency-confusion artifact designed to be resolved from public npm ahead of an internal package of the same name. The generic name, self-referential high-version pin, and install-time beacon to an attacker-controlled collector match the standard dependency-confusion probe shape.

Malicious versions

2 flagged

99.99.99999.99.99

Indicators of compromise (SHA-256)

8166d7eaf8dab64a6c21d0e0a871c64e213147082a414b93816fb080c8044b1e

9b4c1e61651ca7fc4d5b2dc93bc240ffd6339dfe0fde02e66740517cc9c957bf

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 test1ro (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test1ro across your stack and pipelines.
If you installed it — respond
test1ro 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 test1ro 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 test1ro 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. test1ro on npm has been identified as a malicious package (versions 99.99.99, 999.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020212IN-MAL-2026-020210

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test1ro-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