Which versions of keyed-mutex-map are malicious?

The following npm versions of keyed-mutex-map are flagged malicious: 2.1.2. Treat any of these as compromised.

How do I remediate keyed-mutex-map if I installed it?

Remove keyed-mutex-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 keyed-mutex-map — how do I know if it already compromised me?

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

Yes — keyed-mutex-map is associated with the GHSA-vcgv-x4wj-fr9f, IN-MAL-2026-017798 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 keyed-mutex-map across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for keyed-mutex-map (version 2.1.2).

Malicious package

keyed-mutex-mapnpm

Advisory published Aug 13, 2026Updated Aug 14, 2026

keyed-mutex-map is a confirmed malicious npm package (MAL-2026-14003) that executes malicious code on install (malicious version 2.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in keyed-mutex-map (npm)

MAL-2026-14003

Immediate action

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

npm uninstall keyed-mutex-map

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

2.1.2

Indicators of compromise (SHA-256)

8ef27256ea18da3ac9252e892dee2e8e0ef0f01e00846c4850b43b0eff655ee0

dd45a0cb60ef881a4f011fed410aacced4d83f39457bea6c4f21fa7d09076801

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for keyed-mutex-map (version 2.1.2).
If you installed it — respond
Remove keyed-mutex-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 keyed-mutex-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. keyed-mutex-map on npm has been identified as a malicious package (version 2.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vcgv-x4wj-fr9fIN-MAL-2026-017798

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks keyed-mutex-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