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

pipo-sdknpm

Advisory published Updated

pipo-sdk is a confirmed malicious npm package (MAL-2026-7000) that steals credentials and exfiltrates sensitive data (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pipo-sdk (npm)

MAL-2026-7000
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall pipo-sdk

What this malware does

This package is a dependency-confusion payload published at an abnormally high version (9999.0.0) targeting an internal package name (pipo-sdk). The preinstall lifecycle hook runs node callback.js || true, which collects host identity — hostname, username, platform, and current working directory — via os.hostname(), os.userInfo(), and os.platform(), and transmits that data to pbnuwvwzmktaetcsjyyjlhncsf843r5a5.oast.fun by two channels: (a) a DNS resolution of a subdomain encoding the collected fields under the OAST domain, and (b) an HTTPS POST of a JSON body containing the same fields. Any host that runs npm install — for example, an internal build system whose resolver picks the public 9999.0.0 over a legitimate internal version — will silently beacon its identity to the third-party OAST endpoint. The bug-bounty / research framing in the package metadata does not change the installer-side behavior: unsolicited host-identity exfiltration fires on install regardless of consent, and the resolver-hijack version pin ensures the payload is preferred over legitimate internal artifacts.

Malicious versions

1 flagged
9999.0.0

Indicators of compromise (SHA-256)

259159c0505b819905dcaf53172d98a4fd590a9ae1a40f87d2be4c1a7fdc4065

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for pipo-sdk (version 9999.0.0).

  2. If you installed it — respond

    pipo-sdk is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If pipo-sdk 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. pipo-sdk on npm has been identified as a malicious package (version 9999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008122

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks pipo-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

pipo-sdk (npm) malicious package — MAL-2026-7000 | O3 Security