Malicious code in @viertechjs/wb (npm)
Description
The npm package @viertechjs/wb versions 6.0.0-vier.3 through 6.0.0-vier.8 contains malicious code or depends on a component with malicious code. Installation or use of this package can lead to full compromise of the affected system. Secrets and keys stored on compromised systems should be rotated immediately from a secure environment. Removal of the package alone may not fully eliminate the threat due to potential persistent malicious activity.
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 @viertechjs/wb in specific versions (6.0.0-vier.3, 6.0.0-vier.4, 6.0.0-vier.5, 6.0.0-vier.6, 6.0.0-vier.7, 6.0.0-vier.8) was found to contain malicious code or to consume dependencies that include malicious code. According to sources including Amazon Inspector and GHSA malware advisories, any system with this package installed should be considered fully compromised. The malicious code presence implies that attackers may have gained control over the system, necessitating immediate secret and key rotation from a different, uncompromised machine. The package removal is recommended but may not guarantee full remediation due to possible persistent compromise.
Potential Impact
Systems with the affected versions of @viertechjs/wb installed are considered fully compromised. Attackers may have gained complete control, risking exposure of all stored secrets and keys. The compromise could allow unauthorized access, data theft, or further malicious activity. Because the malicious code may persist beyond package removal, the threat is severe and remediation requires comprehensive incident response.
Defensive Guidance
Remove the affected @viertechjs/wb package versions immediately. Rotate all secrets and keys stored on the compromised system from a separate, secure machine. Conduct a thorough investigation and remediation of the affected system to identify and remove any persistent malicious components. There is no official patch or fix available; thus, the best mitigation is to avoid using these package versions and to treat affected systems as compromised.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-15832
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-3f73-cx58-g87j"]
- Ecosystems
- ["npm"]
Threat ID: 6a9ad4e9acd9273b49b676f4
Added to database: 09/04/2026, 14:25:45 UTC
Last enriched: 09/07/2026, 17:39:30 UTC
Last updated: 10/01/2026, 23:03:16 UTC
Views: 23
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.
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.