Skip to content
supplychainattack.orgSupply chain attack incident catalog
containedcritical

Malicious code in @noobaihome/amis-uni-area-widget (npm)

The npm package @noobaihome/amis-uni-area-widget contained malicious code in scripts/install.js that executed during npm preinstall, exfiltrating system information, downloading and executing arbitrary shell scripts, and probing internal corporate networks via SSRF.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Any developer or CI/CD system installing @noobaihome/amis-uni-area-widget via npm
Ecosystems
Attack vectors
Affected entities
  • @noobaihome/amis-uni-area-widgetMultiple versions contained malicious install.js script

The npm package @noobaihome/amis-uni-area-widget was found to contain malicious code in its scripts/install.js file that executed automatically during the npm preinstall phase. The malicious script performed three attacker-controlled actions on the installer's host system.\n\nFirst, the script unconditionally beaconed installer identifiers (process ID, base64-encoded working directory, base64-encoded INIT_CWD environment variable, and a marker) over plain HTTP to a hardcoded bare-IP endpoint at http://49.232.169.67:43817/bsrc-r260. Second, when a parent build manifest matched an internal marker, the script downloaded an unpinned and unverified shell script from http://49.232.169.67:80/slt via curl (with wget fallback) and executed it via /bin/sh using spawnSync, granting the attacker arbitrary code execution on the installer at install time. Third, the script fetched an internal-network endpoint at http://bsrc-ssrf.n.baidu-int.com/bsrc_uid (reachable only from inside a specific corporate network) and forwarded the base64-encoded response back to the same callback IP, characteristic of SSRF-driven internal reconnaissance.\n\nThe destination IP address has no documented relationship to any legitimate package publisher, and all behaviors executed automatically without user interaction. The incident was identified by the OpenSSF malicious-packages project and reported via GitHub Advisory GHSA-932g-6p3v-rp3w.

Indicators of compromise

Domains
  • bsrc-ssrf.n.baidu-int.com
IPs
  • 49.232.169.67

Remediation

  • Immediately uninstall @noobaihome/amis-uni-area-widget from all systems
  • Audit npm install logs and CI/CD pipelines for evidence of this package installation
  • Review network logs for outbound connections to 49.232.169.67:43817 and 49.232.169.67:80
  • Assume any system that installed this package may be compromised; conduct forensic analysis and consider credential rotation
  • Use npm audit to identify any remaining vulnerable versions in dependency trees
  • Implement package pinning and integrity verification for critical dependencies
  • Consider using private npm registries or package allowlists to prevent installation of untrusted packages

Sources

  1. GitHub Advisory GHSA-932g-6p3v-rp3w · GitHub Advisory Database

Cite this entry

"Malicious code in @noobaihome/amis-uni-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-uni-area-widget-npm-1nhc7d

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. resolvedcritical

    Malicious code in autbank-core (npm)

    The npm package autbank-core contained malicious preinstall and postinstall lifecycle hooks that exfiltrated environment variables, credentials, and system information to a hardcoded webhook.site endpoint during installation.

    npmCompromised package
  2. resolvedcritical

    Malicious code in adxaa (npm)

    The npm package adxaa contained obfuscated malicious JavaScript designed to target users of a specific WordPress site. The payload exfiltrates session data, deletes accounts, and hijacks credentials via email overwrite and password reset.

    npmCompromised package
  3. resolvedcritical

    Malicious code in upload-to-gcp (npm)

    upload-to-gcp@3.2.1 (npm) contains malicious code in its postinstall script that exfiltrates host identifiers to an attacker-controlled endpoint. The package masquerades as a Google Cloud Platform utility but performs unauthorized telemetry collection at install time.

    npmCompromised package
  4. resolvedcritical

    Malicious code in akamai-sensor (npm)

    A malicious npm package named akamai-sensor impersonated Akamai's legitimate sensor_data anti-bot SDK. The package contained hidden JavaScript code concealed using invisible Unicode characters and implemented a dynamic command-and-control channel via a Google Calendar dead-drop, enabling arbitrary code execution on installation.

    npmCompromised packageTyposquatting