px8mynpm
px8my is a confirmed malicious npm package (MAL-2026-10104) that executes malicious code on install (malicious versions 1.0.13, 1.0.22, 1.0.23…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in px8my (npm)
What this malware does
px8my's main entry is a browser-side script that injects a full-screen iframe pointing at a hardcoded remote URL (https://mfmz.gzhrjq.cn/H.html?c=0gjr). The tarball also ships update_px8my.sh, a maintainer helper that rewrites the redirect domain in px.js, bumps the patch version, runs npm publish, then calls the jsDelivr purge API — documenting an operational model in which the npm registry + jsDelivr CDN are used as a mutable redirect distribution channel with the destination domain rotated on demand. Installing this as an npm dependency does not directly harm the installer: there are no lifecycle scripts, and require()ing the module in Node would throw because it references document. The impact surface is downstream websites/end-users that load px8my/px.js via the jsDelivr CDN, which are redirected to the maintainer-controlled destination. The package has no library value; it exists to abuse npm namespace + jsDelivr as a redirector. Because the installer is not directly attacked but the package is clearly designed as an abuse vehicle, route to human review for a takedown decision.
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for px8my (34 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging px8my across your stack and pipelines.
If you installed it — respond
Remove px8my from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If px8my 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 px8my 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks px8my-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.