Which versions of pocpoc2626 are malicious?

The following npm versions of pocpoc2626 are flagged malicious: 99.99.9998, 100.0.5. Treat any of these as compromised.

How do I remediate pocpoc2626 if I installed it?

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

If pocpoc2626 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.

How do I find pocpoc2626 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pocpoc2626 (2 malicious versions).

Malicious package

pocpoc2626npm

Advisory published May 4, 2026Updated May 12, 2026

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

Malicious code in pocpoc2626 (npm)

MAL-2026-3328

Immediate action

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

npm uninstall pocpoc2626

What this malware does

The package pocpoc2626 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'pocpoc2626' @ 99.99.9998 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

2 flagged

99.99.9998100.0.5

Indicators of compromise (SHA-256)

0176ec0fde390432553ec3dffa91438e5e923d23549ef4b836bc91de5259a21d

b4744f62b321959f843350974284f2a501ea2e1e80c5ca0d9a2affd0f620b9c4

4a43e5357592b2bbbe0c68be3960ac829ab988a15b57d63df5ab954c9d0b5b09

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for pocpoc2626 (2 malicious versions).
If you installed it — respond
pocpoc2626 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 pocpoc2626 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. pocpoc2626 on npm has been identified as a malicious package (versions 99.99.9998, 100.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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