Malicious code in @noobaihome/amis-simple-area-widget (npm)
@noobaihome/amis-simple-area-widget@1.0.0 on npm contains malicious code in a preinstall hook that performs blind SSRF/network reconnaissance, fetching internal Baidu network content and exfiltrating it to an attacker-controlled IP. The package is a dependency-confusion lure targeting an internal @noobaihome scope.
- Disclosed
- Last updated
- Blast radius
- Any developer or CI/CD system installing @noobaihome/amis-simple-area-widget@1.0.0 from npm; potential network reconnaissance of internal Baidu infrastructure from compromised environments.
- Ecosystems
- Attack vectors
- Affected entities
- @noobaihome/amis-simple-area-widget · 1.0.0
@noobaihome/amis-simple-area-widget@1.0.0 was published to npm as a fake widget package. The main distribution files (dist/renderer.umd.js and dist/plugin.umd.js) are empty stubs, while the actual malicious functionality is hidden in scripts/install.js, executed via a preinstall lifecycle hook during npm install.
The preinstall script performs a blind SSRF attack: it fetches content from http://bsrc-ssrf.n.baidu-int.com/bsrc_uid (an internal-only Baidu host) and POSTs the base64url-encoded response along with a marker string 'BSRC_RCE_R255_7e49c2' to http://49.232.169.67:43817/bsrc-r255. This allows an attacker to probe internal network resources from any compromised installer environment.
The package name is a dependency-confusion attack vector, mimicking an internal @noobaihome scope to trick developers or automated systems into installing the malicious public package. Installation causes outbound traffic carrying sensitive internal network content to an attacker-controlled endpoint, regardless of any stated bug-bounty framing.
The incident was identified and credited to the OpenSSF malicious-packages repository.
Indicators of compromise
- Packages
- @noobaihome/amis-simple-area-widget@1.0.0
- Domains
- bsrc-ssrf.n.baidu-int.com
- IPs
- 49.232.169.67
Remediation
- Immediately uninstall @noobaihome/amis-simple-area-widget@1.0.0 from all environments
- Audit npm install logs and CI/CD pipelines for any installation of this package
- Review outbound network traffic from affected systems for connections to 49.232.169.67:43817
- Implement npm package allow-lists or private registry mirrors to prevent dependency-confusion attacks
- Monitor for similar typosquatting or scope-confusion packages targeting internal namespaces
- Consider using npm audit and supply-chain security tools to detect malicious packages before installation
Sources
- GitHub Advisory GHSA-jprv-2653-h4xc · GitHub Advisory Database
Cite this entry
"Malicious code in @noobaihome/amis-simple-area-widget (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 10, 2026; last updated August 10, 2026. https://supplychainattack.org/incident/malicious-code-in-noobaihome-amis-simple-area-widget-npm-1b8ahq
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in mtslink-depconf-probe-profileusername (npm)
The npm package mtslink-depconf-probe-profileusername contained malicious code designed to probe for internal namespace dependencies and exfiltrate install-time telemetry via DNS lookups to attacker-controlled infrastructure. The package was identified as a dependency-confusion probe targeting internal package namespaces.
npmCompromised packageDependency confusion - resolvedcritical
Malicious code in bcc-design (npm)
bcc-design@9999.0.0 on npm is a dependency-confusion beacon package with no legitimate functionality. Its postinstall script exfiltrates the installer's hostname and system metadata to an attacker-controlled IP endpoint.
npmDependency confusionCompromised package - containedcritical
Malicious code in bcc-design-icons (npm)
bcc-design-icons@9999.0.0 on npm contains malicious postinstall script that exfiltrates hostname and package name to attacker-controlled IP 91.201.215.48:8000. The package lacks expected icon-library functionality and exhibits characteristics of a dependency-confusion attack targeting internal/private npm installers.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in fastly-vcl-language-client (npm)
The npm package fastly-vcl-language-client contained malicious code in a preinstall script that collected system information and CI environment variables, exfiltrating data to an external webhook endpoint. The package appears to be a dependency-confusion attack targeting internal Fastly tooling.
npmCompromised packageDependency confusion