websight2-p2pnpm
websight2-p2p is a confirmed malicious npm package (MAL-2026-10698) that executes malicious code on install (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 websight2-p2p (npm)
What this malware does
The package ships a single file, index.html, which is declared as the package main. On render, index.html fetches https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight with a cache-busting query string and injects the response into the page via document.open(); document.write(html);, executing whatever HTML/JS the remote returns. The URL is pinned to the mutable main branch with no commit SHA and no integrity/hash verification, so the repository owner (or anyone with write access to that Bitbucket repo) can change the executed payload at any time. The package has no npm lifecycle scripts and the main is HTML rather than JS, so npm install and require() are themselves inert — the fetch-and-execute path only fires when the HTML is opened in a browser, which is the package's advertised use. Author metadata is empty ("author": "", empty keywords, generic ISC license, one-line description), which is unusual for a loader that proxies arbitrary remote code into a browser context.
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 websight2-p2p (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging websight2-p2p across your stack and pipelines.
If you installed it — respond
Remove websight2-p2p 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 websight2-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 websight2-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 websight2-p2p-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.