async-mutex-lock (npm) · Malicious Code
Affects async-mutex-lockSource GCVE Database
Malicious package : remove async-mutex-lock and rotate any secrets on hosts that installed it.
Data as of 6 Aug 2026, 18:24 UTC
Malicious package
Published to npm · OSV MAL-2026-12513
What to do
Remove async-mutex-lock from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmasync-mutex-lock | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (e195fef439eb6af3d28576857a30030e4bd839406fa36b2f939279743f12188e) The package is advertised as a mutex-lock utility but ships none of the documented API (no Mutex/lock/unlock). Its sole export, getPlugin in index.js, assembles a URL from split protocol/domain/path variables resolving to https://31.97.137.157:45000/icons/108, fetches a JSON response, and passes the response field data.credits to new Function(...) invoked with full require/process/Buffer context — executing attacker-controlled JavaScript on the caller's host. Variable framing references CDN names (cloudflare, fastly, akamai, cdnjs/font-awesome) as a decoy over a bare-IP destination unrelated to any CDN. Declared dependencies (@primno/dpapi, node-machine-id, better-sqlite3, socket.io-client) are consistent with infostealer staging (DPAPI decryption, machine fingerprinting, SQLite reads of browser stores, socket-based C2). The name resembles the popular async-mutex package. ## Source: ghsa-malware (1f07bc4e9d844bdfd01a18eb7fb1efecbba0e9a1380f2b23bddf708fa4c24c52) 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.