Which versions of ambera are malicious?

The following npm versions of ambera are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate ambera if I installed it?

ambera is a typosquat — you almost certainly intended a legitimately-named package. Remove ambera, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed ambera — how do I know if it already compromised me?

If ambera 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 ambera part of a known attack campaign?

Yes — ambera is associated with the IN-MAL-2026-018324, IN-MAL-2026-018325 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 ambera 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 ambera (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ambera across your stack and pipelines.

Malicious package

amberanpm

ambera is a confirmed malicious npm package (MAL-2026-14225) that typosquats a legitimate package to trick installs (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ambera (npm)

MAL-2026-14225

Immediate action

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

npm uninstall ambera

What this malware does

The package presents itself as a zero-dependency SVG helper, but its exported getPlugin() function performs an HTTPS GET to the hardcoded host https://api.avax-test.dev/ext/bc/rpc with TLS verification disabled (rejectUnauthorized: false) and passes the response body directly to new Function('require', data)(require). Any caller of getPlugin() executes whatever JavaScript the remote host returns, with the Node require function injected — effectively arbitrary remote code execution on the caller's machine. The destination host api.avax-test.dev is a lookalike of the legitimate Avalanche Fuji RPC endpoint api.avax-test.network, and the Avalanche/Snowtrace variable naming is cover-story labeling: the package's stated SVG purpose has no network or blockchain functionality. Combined with the disabled TLS verification, this is a deliberately concealed remote-exec channel embedded in an unrelated utility.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

0a436ba1448ab5bbc5819828e8082b05598893b24f4578c8a37ea3a7ef4c732e

d24544221570c21c3b710d7c4d39ed76e7cc8b43a555bb7c8e6fefa78aa3f625

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ambera (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ambera across your stack and pipelines.
If you installed it — respond
ambera is a typosquat — you almost certainly intended a legitimately-named package. Remove ambera, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If ambera 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 ambera 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. ambera on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018324IN-MAL-2026-018325

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ambera-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database