MAL-2026-13690 Malicious code in @noobaihome/amis-uni-area-widget (npm)
Malicious package
Published
MAL-2026-13690 is a malicious package: @noobaihome/amis-uni-area-widget (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-13690/ (Markdown: https://insights.sbomify.com/MAL-2026-13690/index.md)
- Package
- @noobaihome/amis-uni-area-widget
- Registry
- npm
What is MAL-2026-13690?
MAL-2026-13690 is a malicious package in @noobaihome/amis-uni-area-widget, published on 10 Aug 2026.
Official description
scripts/install.js runs during npm preinstall and performs three attacker-beneficial actions against the installer host. First, it unconditionally beacons installer identifiers (pid, base64-encoded process.cwd(), base64-encoded process.env.INIT_CWD, and a marker) over plain HTTP to the hardcoded bare-IP endpoint http://49.232.169.67:43817/bsrc-r260. Second, when a parent build manifest matches an internal marker, it downloads a shell script from http://49.232.169.67:80/slt via curl (with a wget fallback) and pipes the response into /bin/sh through spawnSync, giving the remote host arbitrary code execution on the installer at install time. Third, it fetches http://bsrc-ssrf.n.baidu-int.com/bsrc_uid — an internal-network endpoint reachable only from inside a specific corporate network — and forwards the base64-encoded response body back to the same 49.232.169.67:43817 callback, characteristic of an SSRF-driven internal reconnaissance probe. The destination is a bare IPv4 address on plain HTTP with no relationship to any documented publisher, the fetched shell script is unpinned and unverified, and all three behaviors fire automatically on npm install.
What should I do about MAL-2026-13690?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.