Which versions of ambient-map are malicious?

The following npm versions of ambient-map are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate ambient-map if I installed it?

Remove ambient-map from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed ambient-map — how do I know if it already compromised me?

If ambient-map was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is ambient-map part of a known attack campaign?

Yes — ambient-map is associated with the RLMA-2025-06059 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 ambient-map across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ambient-map (version 99.99.99).

Malicious package

ambient-mapnpm

Advisory published Dec 5, 2025Updated Dec 23, 2025

ambient-map is a confirmed malicious npm package (MAL-2025-192324) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ambient-map (npm)

MAL-2025-192324

Immediate action

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

npm uninstall ambient-map

What this malware does

The package ambient-map was found to contain malicious code.

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

4f03e10d2eec7143fda8062e504341041a8123bc6f2a0d7223ce9ced959b7dd1

4640097b479b152f526e8afd403add99438874ca493c652d6ce436ed97c02226

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for ambient-map (version 99.99.99).
If you installed it — respond
Remove ambient-map from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If ambient-map was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. ambient-map on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06059

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ambient-map-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