Which versions of test1df23 are malicious?

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

How do I remediate test1df23 if I installed it?

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

If test1df23 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is test1df23 part of a known attack campaign?

Yes — test1df23 is associated with the IN-MAL-2026-020209 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 test1df23 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for test1df23 (version 99.99.99).

Malicious package

test1df23npm

Advisory published Sep 21, 2026Updated Sep 21, 2026

test1df23 is a confirmed malicious npm package (MAL-2026-16312) 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 test1df23 (npm)

MAL-2026-16312

Immediate action

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

npm uninstall test1df23

What this malware does

package.json declares preinstall and postinstall hooks that execute index.js on npm install. index.js issues an HTTP GET to the hardcoded bare IP 128.199.122.145 over plain HTTP, with the package name embedded in the query string (http://128.199.122.145/?test1df23). The beacon fires automatically at install time, leaking the installer's outbound IP and confirming successful execution on the installer's host to the operator of that IP. The package name and near-empty payload are consistent with a dependency-confusion or typosquat probe.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

67708642854d76da722a8130de47a8fb7fd23f0035cf646f1bf16d97419e5756

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for test1df23 (version 99.99.99).
If you installed it — respond
test1df23 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 test1df23 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. test1df23 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-020209

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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