websight-p2pnpm
websight-p2p is a confirmed malicious npm package (MAL-2026-10697) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in websight-p2p (npm)
What this malware does
The package ships a single index.html whose body fetches https://loader.p2pgames.workers.dev/ (with header x-access: p2p) and passes the response to document.write(), executing whatever HTML/JavaScript the worker returns. There is no integrity check, no version pinning, and the worker can serve different content per request or per caller. There are no npm lifecycle hooks, so installing the package does not execute code on the developer's machine; the remote-execution behavior only fires when the HTML is opened in a browser by an end user of a consumer application that ships this file. Concerns: any site embedding this file fully delegates page-script control to the author-controlled worker (mutable, unpinned, no SRI), so today's benign content can become tomorrow's attacker payload without any package change. This does not fit the install-time-RCE or active-attack threshold (no install/import-time execution against the installer; no exfiltration of installer secrets), but the runtime fetch-and-execute pattern from a mutable author-controlled endpoint warrants human review before publishing a verdict.
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
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for websight-p2p (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging websight-p2p across your stack and pipelines.
If you installed it — respond
websight-p2p 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.
Did it already run?
If websight-p2p 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 websight-p2p 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 websight-p2p-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.