Which versions of @noobaihome/amis-simple-area-widget are malicious?

The following npm versions of @noobaihome/amis-simple-area-widget are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @noobaihome/amis-simple-area-widget if I installed it?

@noobaihome/amis-simple-area-widget establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed @noobaihome/amis-simple-area-widget — how do I know if it already compromised me?

If @noobaihome/amis-simple-area-widget 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.

Is @noobaihome/amis-simple-area-widget part of a known attack campaign?

Yes — @noobaihome/amis-simple-area-widget is associated with the IN-MAL-2026-017244 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @noobaihome/amis-simple-area-widget across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @noobaihome/amis-simple-area-widget (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @noobaihome/amis-simple-area-widget across your stack and pipelines.

Malicious package

@noobaihome/amis-simple-area-widgetnpm

@noobaihome/amis-simple-area-widget is a confirmed malicious npm package (MAL-2026-13689) that opens a backdoor for remote access (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-13689

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @noobaihome/amis-simple-area-widget

What this malware does

@noobaihome/[email protected] advertises an AI Suda amis area-chart widget, but dist/renderer.umd.js and dist/plugin.umd.js are empty stubs (module.exports = {}). The only functional code is scripts/install.js, invoked from a preinstall lifecycle hook, which on npm install fetches http://bsrc-ssrf.n.baidu-int.com/bsrc_uid (an internal-only Baidu host reachable only from an installer inside that network perimeter) and POSTs the base64url-encoded response, along with a marker string 'BSRC_RCE_R255_7e49c2', to a hardcoded external IP callback at http://49.232.169.67:43817/bsrc-r255. The package name is a dependency-confusion lure against an internal @noobaihome scope. Installing the package causes outbound traffic from the installer's environment to an attacker-chosen public IP carrying content only reachable from inside the target's private network — a blind SSRF / dependency-confusion probe, regardless of any stated bug-bounty framing.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

642f206459c4677892954c26736b990c72bb01ae9383f917ab664b38d977819f

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @noobaihome/amis-simple-area-widget (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @noobaihome/amis-simple-area-widget across your stack and pipelines.
If you installed it — respond
@noobaihome/amis-simple-area-widget establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If @noobaihome/amis-simple-area-widget 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 @noobaihome/amis-simple-area-widget 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

No. @noobaihome/amis-simple-area-widget on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017244

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @noobaihome/amis-simple-area-widget-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database