Malicious code in turbo-ws (npm)
The npm package 'turbo-ws' version 1.0.0 includes a malicious dependency fetched directly from an unrelated GitHub repository without integrity checks. This dependency executes code during installation, potentially compromising any system that installs the package. The package falsely advertises having zero dependencies, misleading users. Systems with this package installed should be considered fully compromised, and all secrets and keys on those systems should be rotated immediately. Removal of the package does not guarantee full remediation due to possible persistent malicious control.
AI Analysis
Technical Summary
The 'turbo-ws' npm package version 1.0.0 declares a single dependency 'node-net-pool' sourced from an HTTPS tarball URL pointing to the 'main' branch of an unrelated GitHub account, rather than a versioned registry package. This unpinned, unchecked source allows arbitrary code execution during npm install lifecycle scripts. The package's postinstall script requires 'node-net-pool', executing its code on the installer's machine. Control of the referenced GitHub account equates to control over code executed on every installer of 'turbo-ws'. The package description misleadingly claims 'zero dependencies', contradicting the actual manifest.
Potential Impact
Any computer with 'turbo-ws' version 1.0.0 installed is considered fully compromised. Attackers controlling the malicious dependency can execute arbitrary code on the affected system, potentially stealing secrets, keys, and sensitive data. Immediate rotation of all secrets and keys stored on the compromised machine is necessary. Removing the package alone may not eliminate all malicious software or backdoors introduced during installation.
Mitigation Recommendations
Users should immediately remove the 'turbo-ws' package version 1.0.0 from their systems. All secrets and keys stored on affected machines must be rotated from a separate, uncompromised device. Due to the nature of the compromise, a full system reinstallation or forensic analysis is recommended to ensure complete remediation. No official patch or fixed version is currently indicated; therefore, avoidance of this package version is advised.
Malicious code in turbo-ws (npm)
Description
The npm package 'turbo-ws' version 1.0.0 includes a malicious dependency fetched directly from an unrelated GitHub repository without integrity checks. This dependency executes code during installation, potentially compromising any system that installs the package. The package falsely advertises having zero dependencies, misleading users. Systems with this package installed should be considered fully compromised, and all secrets and keys on those systems should be rotated immediately. Removal of the package does not guarantee full remediation due to possible persistent malicious control.
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 'turbo-ws' npm package version 1.0.0 declares a single dependency 'node-net-pool' sourced from an HTTPS tarball URL pointing to the 'main' branch of an unrelated GitHub account, rather than a versioned registry package. This unpinned, unchecked source allows arbitrary code execution during npm install lifecycle scripts. The package's postinstall script requires 'node-net-pool', executing its code on the installer's machine. Control of the referenced GitHub account equates to control over code executed on every installer of 'turbo-ws'. The package description misleadingly claims 'zero dependencies', contradicting the actual manifest.
Potential Impact
Any computer with 'turbo-ws' version 1.0.0 installed is considered fully compromised. Attackers controlling the malicious dependency can execute arbitrary code on the affected system, potentially stealing secrets, keys, and sensitive data. Immediate rotation of all secrets and keys stored on the compromised machine is necessary. Removing the package alone may not eliminate all malicious software or backdoors introduced during installation.
Mitigation Recommendations
Users should immediately remove the 'turbo-ws' package version 1.0.0 from their systems. All secrets and keys stored on affected machines must be rotated from a separate, uncompromised device. Due to the nature of the compromise, a full system reinstallation or forensic analysis is recommended to ensure complete remediation. No official patch or fixed version is currently indicated; therefore, avoidance of this package version is advised.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-16440
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-3933-m2c5-xfm8"]
- Ecosystems
- ["npm"]
Threat ID: 6ac139a8a43b0b3b89d69aba
Added to database: 10/03/2026, 17:21:44 UTC
Last enriched: 10/03/2026, 17:37:43 UTC
Last updated: 10/03/2026, 22:37:28 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.