Which versions of test1sdsd2 are malicious?

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

How do I remediate test1sdsd2 if I installed it?

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

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

Yes — test1sdsd2 is associated with the IN-MAL-2026-020214 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 test1sdsd2 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 test1sdsd2 (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 test1sdsd2 across your stack and pipelines.

Malicious package

test1sdsd2npm

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

Malicious code in test1sdsd2 (npm)

MAL-2026-16316

Immediate action

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

npm uninstall test1sdsd2

What this malware does

Package [email protected] declares preinstall and postinstall hooks in package.json that execute index.js on npm install. index.js performs an HTTP GET to the hardcoded bare IP http://128.199.122.145/?test1sdsd2, embedding the package name in the query string, which confirms code execution on the installer's machine and leaks install-signal (package name, implicit source IP, timing) to an attacker-controlled endpoint. The version number 99.99.99 combined with the beacon shape is the canonical dependency-confusion probe pattern used to detect resolution of an internal package name against a public registry. The package ships no legitimate library functionality.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

3c7bd7c5932337e17adaf4900cb7e29766fe6b5307bd170b38660dd05497ebdc

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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