websight-p2pnpm

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.