Which versions of async-mutex-v3 are malicious?

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

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

async-mutex-v3 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — async-mutex-v3 is associated with the IN-MAL-2026-014928 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-v3 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-v3 (version 3.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-v3 across your stack and pipelines.

Malicious package

async-mutex-v3npm

async-mutex-v3 is a confirmed malicious npm package (MAL-2026-12514) that steals credentials and exfiltrates sensitive data (malicious version 3.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in async-mutex-v3 (npm)

MAL-2026-12514

Immediate action

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

npm uninstall async-mutex-v3

What this malware does

Package name typosquats async-mutex but ships unrelated functionality. The default export getPlugin in index.js issues an HTTP request to a hardcoded bare IP endpoint (http://46.183.25.232:45000/icons/108) and passes the response's credits field into new Function('require','module',...,'Promise', data.credits), executing attacker-controlled JavaScript with Node privileges (access to require, process, Buffer). Cover-story variable names (IconProvider, iconDomain referencing cloudflare/fastly/akamai/gcore, path /ajax/libs/font-awesome/..., header bearrtoken: 'logo') frame the code as an icon CDN helper, while the actually-used path hits the bare IP. Declared dependencies (better-sqlite3, @primno/dpapi, node-machine-id) are consistent with a credential-stealer post-exploitation pipeline. Any consumer that requires this package and invokes the default export executes whatever JavaScript the remote server returns.

Malicious versions

1 flagged

3.1.0

Indicators of compromise (SHA-256)

699abe52cb380ae997f200e0615bfce84cd52d11b98a54244ce5b30478fab336

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for async-mutex-v3 (version 3.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-v3 across your stack and pipelines.
If you installed it — respond
async-mutex-v3 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If async-mutex-v3 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-v3 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-v3 on npm has been identified as a malicious package (version 3.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014928

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks async-mutex-v3-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database