Malicious code in async-lock-queue (npm)
The npm package async-lock-queue version 3.0.1 contains malicious code or depends on a package with malicious code. Installing or running this package can lead to a full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not eliminate all malicious software introduced by it.
AI Analysis
Technical Summary
The npm package async-lock-queue version 3.0.1 has been identified as containing malicious code or relying on a malicious dependency. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code potentially grants full control to an outside entity, posing a severe security risk. Immediate secret and key rotation is advised from a separate, uncompromised system. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts.
Potential Impact
Systems with async-lock-queue version 3.0.1 installed or running are at risk of full compromise, including unauthorized access and control by attackers. Sensitive information such as secrets and keys stored on the system may be exposed and should be rotated. The presence of this package can lead to persistent malicious activity beyond the package itself.
Mitigation Recommendations
Remove the async-lock-queue package version 3.0.1 immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure machine. Because the system may be fully compromised, consider a full system rebuild or forensic analysis to ensure removal of all malicious components. Monitor for any suspicious activity related to this compromise.
Malicious code in async-lock-queue (npm)
Description
The npm package async-lock-queue version 3.0.1 contains malicious code or depends on a package with malicious code. Installing or running this package can lead to a full compromise of the affected system. Secrets and keys stored on the compromised system should be rotated immediately from a different, secure machine. Removing the package alone may not eliminate all malicious software introduced by it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The npm package async-lock-queue version 3.0.1 has been identified as containing malicious code or relying on a malicious dependency. According to sources including Amazon Inspector and the GitHub Security Advisory for malware, any system with this package installed or running should be considered fully compromised. The malicious code potentially grants full control to an outside entity, posing a severe security risk. Immediate secret and key rotation is advised from a separate, uncompromised system. Due to the nature of the compromise, simply uninstalling the package does not guarantee removal of all malicious artifacts.
Potential Impact
Systems with async-lock-queue version 3.0.1 installed or running are at risk of full compromise, including unauthorized access and control by attackers. Sensitive information such as secrets and keys stored on the system may be exposed and should be rotated. The presence of this package can lead to persistent malicious activity beyond the package itself.
Defensive Guidance
Remove the async-lock-queue package version 3.0.1 immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure machine. Because the system may be fully compromised, consider a full system rebuild or forensic analysis to ensure removal of all malicious components. Monitor for any suspicious activity related to this compromise.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13999
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-h6x7-5w93-p56j"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a7f43f1bf8831d5395d767d
Added to database: 08/14/2026, 16:36:01 UTC
Last enriched: 08/14/2026, 16:48:27 UTC
Last updated: 08/14/2026, 16:48:27 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.