MAL-2026-7000 Malicious code in pipo-sdk (npm)
Malicious package
Published
MAL-2026-7000 is a malicious package: pipo-sdk (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-7000/ (Markdown: https://insights.sbomify.com/MAL-2026-7000/index.md)
- Package
- pipo-sdk
- Registry
- npm
What is MAL-2026-7000?
MAL-2026-7000 is a malicious package in pipo-sdk, published on 8 Jul 2026.
Official description
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.What should I do about MAL-2026-7000?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.