Which versions of test12vv36 are malicious?

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

How do I remediate test12vv36 if I installed it?

test12vv36 is a typosquat — you almost certainly intended a legitimately-named package. Remove test12vv36, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

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

Malicious package

test12vv36npm

test12vv36 is a confirmed malicious npm package (MAL-2026-16311) that typosquats a legitimate package to trick installs (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test12vv36 (npm)

MAL-2026-16311

Immediate action

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

npm uninstall test12vv36

What this malware does

[email protected] declares both preinstall and postinstall lifecycle hooks that execute index.js on npm install. index.js issues an HTTP GET to a hardcoded bare-IP endpoint at http://128.199.122.145/?test12vv36, sending the package name in the query string and disclosing the installer's source IP to the operator of that host. The version number (99.99.99) and package.json shape (dependency on a typosquat name 'requests@^0.3.0' plus a duplicate misspelled 'Dependencies' key) are consistent with a dependency-confusion or proof-of-concept publish rather than a functional library. Installing the package causes unauthenticated, unencrypted outbound network activity to attacker-controlled infrastructure at install time, confirming successful installation on the host.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

9292921d0fe368160694717f99eca753070a4249696c72b2f1bff9594cab40be

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test12vv36 (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test12vv36 across your stack and pipelines.
If you installed it — respond
test12vv36 is a typosquat — you almost certainly intended a legitimately-named package. Remove test12vv36, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If test12vv36 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 test12vv36 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. test12vv36 on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020211

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test12vv36-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database