Which versions of test1gg234 are malicious?

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

How do I remediate test1gg234 if I installed it?

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

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

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

Malicious package

test1gg234npm

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

MAL-2026-16313

Immediate action

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

npm uninstall test1gg234

What this malware does

The package declares both preinstall and postinstall lifecycle hooks that execute index.js, which issues a plaintext HTTP GET to the hardcoded bare IP 128.199.122.145 with the package name in the query string. The beacon fires unconditionally on npm install, confirming to the operator of that host that the package was resolved and installed on the target machine. The package has no other functionality: an empty description, an inflated version (99.99.99), and a manifest that declares a lookalike dependency requests alongside a duplicate capitalized Dependencies key referencing request — the shape of a dependency-confusion probe rather than a functional library.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

dd57f799e0797ede7d18d6a36dd05c31c34d21b4e45d554730a8d08dd310cf73

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

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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