2-loadsight-webnpm
2-loadsight-web is a confirmed malicious npm package (MAL-2026-14363) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in 2-loadsight-web (npm)
What this malware does
The package consists of a minimal HTML wrapper (index.html) whose only behavior is to fetch content from a hardcoded, unpinned URL at https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight, parse the returned HTML, and re-create every <script> element from the response as a live script tag in the host document, causing the fetched JavaScript to execute in the consuming page's origin. The 'raw/main/...' reference is a mutable branch with no commit pin, no hash check, and no signature verification, so the Bitbucket account 'p2p-alt-public' can substitute arbitrary code at any time. package.json has an empty author field and a generic 'Website loader for remote HTML content' description, and main points directly at the wrapper HTML.
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 2-loadsight-web (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging 2-loadsight-web across your stack and pipelines.
If you installed it — respond
Remove 2-loadsight-web 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 2-loadsight-web 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 2-loadsight-web 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 2-loadsight-web-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.