Malicious code in rbac-auth (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cfd069b5aee6494b5fb19754ecc7a98fd39d282a9ea458c46e0bd7045e2c19cb) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (574eb872a7c1d07d6f1a1fc9aa6c1b217b861ad4bc85392ed0576ede596502c2) 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.
AI Analysis
Technical Summary
The 'rbac-auth' npm package versions 1.0.6 and 1.1.6 have been identified as containing malicious code or relying on dependencies that include malicious code. This malicious code can fully compromise any computer where the package is installed or executed. The compromise includes potential unauthorized access to secrets and keys stored on the system. Due to the severity of the compromise, removal of the package alone is insufficient to guarantee system cleanup.
Potential Impact
Systems with 'rbac-auth' versions 1.0.6 or 1.1.6 installed are considered fully compromised. Attackers may have gained full control over the affected system, risking exposure and theft of all stored secrets and keys. The integrity and confidentiality of the system and its data are severely impacted.
Mitigation Recommendations
Remove the 'rbac-auth' package versions 1.0.6 and 1.1.6 immediately. Rotate all secrets and keys from a separate, uncompromised system. Because full system compromise is possible, consider rebuilding or thoroughly cleaning the affected system to ensure removal of all malicious components. No official patch or fix is currently documented; therefore, avoidance of these versions is recommended.
Malicious code in rbac-auth (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (cfd069b5aee6494b5fb19754ecc7a98fd39d282a9ea458c46e0bd7045e2c19cb) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (574eb872a7c1d07d6f1a1fc9aa6c1b217b861ad4bc85392ed0576ede596502c2) 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.
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 'rbac-auth' npm package versions 1.0.6 and 1.1.6 have been identified as containing malicious code or relying on dependencies that include malicious code. This malicious code can fully compromise any computer where the package is installed or executed. The compromise includes potential unauthorized access to secrets and keys stored on the system. Due to the severity of the compromise, removal of the package alone is insufficient to guarantee system cleanup.
Potential Impact
Systems with 'rbac-auth' versions 1.0.6 or 1.1.6 installed are considered fully compromised. Attackers may have gained full control over the affected system, risking exposure and theft of all stored secrets and keys. The integrity and confidentiality of the system and its data are severely impacted.
Mitigation Recommendations
Remove the 'rbac-auth' package versions 1.0.6 and 1.1.6 immediately. Rotate all secrets and keys from a separate, uncompromised system. Because full system compromise is possible, consider rebuilding or thoroughly cleaning the affected system to ensure removal of all malicious components. No official patch or fix is currently documented; therefore, avoidance of these versions is recommended.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-5873
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-vhxh-pphh-cjmr"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a50ba4c68715ace4357ea45
Added to database: 07/10/2026, 09:24:28 UTC
Last enriched: 07/10/2026, 09:38:45 UTC
Last updated: 07/30/2026, 06:25:56 UTC
Views: 7
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.