Which versions of async-mutex-v2 are malicious?

The following npm versions of async-mutex-v2 are flagged malicious: 2.1.0. Treat any of these as compromised.

How do I remediate async-mutex-v2 if I installed it?

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

I already installed async-mutex-v2 — how do I know if it already compromised me?

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

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

Malicious package

async-mutex-v2npm

Malicious code in async-mutex-v2 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10582

Immediate action

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

npm uninstall async-mutex-v2

What this malware does

Package published as 'async-mutex-v2' advertises itself as a Promise-based mutex but ships no mutex implementation. The main entry (index.js) exports getPlugin(), which performs an HTTPS request to https://svganchordev.net/icons/108 and passes the response field data.credits into new Function('require','module',...,'Promise', data.credits), executing attacker-supplied JavaScript with full Node capabilities (require, process, Buffer, etc.) on the caller's host. A separate setDefaultModule routine referencing font-awesome/cdnjs strings acts as a decoy consistent with the icon-themed exfil host. Declared dependencies (@primno/dpapi, better-sqlite3, node-machine-id) are not used by any shipped code and are the standard toolkit for Windows DPAPI decryption, Chromium 'Login Data'/'Cookies' SQLite extraction, and host fingerprinting — capabilities that only make sense when invoked by the remotely-fetched payload. The package name, description ('Promise-based mutex'), and keywords (react, helper, svg) do not match the shipped code or dependencies, indicating a lookalike/cover-story around async-mutex.

Malicious versions

1 flagged

2.1.0

Indicators of compromise (SHA-256)

7df420be80a00abb5efead6e83b37885cc37a347641386c0633719197dcb3dc5

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 async-mutex-v2 (version 2.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging async-mutex-v2 across your stack and pipelines.
If you installed it — respond
async-mutex-v2 is a typosquat — you almost certainly intended a legitimately-named package. Remove async-mutex-v2, 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 async-mutex-v2 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 async-mutex-v2 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. async-mutex-v2 on npm has been identified as a malicious package (version 2.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010523

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks async-mutex-v2-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