Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

pocpoc2626npm

Malicious code in pocpoc2626 (npm) Remove it immediately and rotate any exposed credentials.

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pocpoc2626 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pocpoc2626 across your stack and pipelines.

  2. 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.

  3. Did it already run?

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

  4. How O3 protects you

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

pocpoc2626 (npm) malicious package — MAL-2026-3328 | O3 Security