Malicious code in 2-loadsight-web (npm)
The npm package 2-loadsight-web contained malicious code that fetches and executes arbitrary JavaScript from an unpinned, mutable Bitbucket URL. The package wraps HTML content fetched from https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight and injects it as live script tags into the consuming page, allowing the attacker to execute code in the host document's origin.
- Disclosed
- Last updated
- Blast radius
- Any application that installed the 2-loadsight-web package would execute arbitrary code from the attacker-controlled Bitbucket repository in the consuming page's origin.
- Ecosystems
- Attack vectors
- Affected entities
- 2-loadsight-webnpm package containing malicious code
The npm package 2-loadsight-web was identified as containing malicious code by the OpenSSF malicious-packages project. The package consists of a minimal HTML wrapper (index.html) that fetches content from a hardcoded URL at https://bitbucket.org/p2p-alt-public/p2p-emis/raw/main/GameWebSight.
The fetched HTML is parsed and every element is recreated as a live script tag in the host document, causing the fetched JavaScript to execute in the consuming page's origin. The URL references a mutable branch with no commit pin, no hash check, and no signature verification, allowing the Bitbucket account 'p2p-alt-public' to substitute arbitrary code at any time.
The package.json contains an empty author field and a generic description ('Website loader for remote HTML content'), with the main entry point directly referencing the wrapper HTML. This design pattern enables arbitrary code execution in any application that installs and uses this package.
Indicators of compromise
- Packages
- 2-loadsight-web
- Domains
- bitbucket.org
Remediation
- Remove the 2-loadsight-web package from all projects and dependencies
- Audit any applications that installed this package for signs of compromise or data exfiltration
- Review access logs for the period when the package was installed to detect any suspicious activity
- Consider rotating credentials and secrets if they may have been exposed to code executing in the application's origin
Sources
- GitHub Advisory GHSA-4f5v-fg99-x9xc · GitHub Advisory Database
Cite this entry
"Malicious code in 2-loadsight-web (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 23, 2026; last updated August 23, 2026. https://supplychainattack.org/incident/malicious-code-in-2-loadsight-web-npm-1gef5n
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in svelte-dim-kit
The npm package svelte-dim-kit was found to contain malware, potentially giving attackers full control of affected systems. All systems with this package installed should be considered compromised and secrets/keys rotated immediately from a different computer.
npmCompromised package - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in stillm4ddpocs-rtest-bravo (npm)
The npm package stillm4ddpocs-rtest-bravo contained malicious code in its preinstall script that automatically executed during installation, collecting system information and internal package metadata and exfiltrating it to a third-party Interactsh collector via HTTPS and DNS tunneling.
npmCompromised package