Malicious code in docker-api-client (npm)
The npm package [email protected] is a malicious typosquat of the legitimate dockerode package. When required, it collects extensive environment information including hostname, username, home directory, platform, current working directory, and the entire process environment variables. This data is serialized, encoded, and exfiltrated via HTTPS GET requests to a Telegram bot controlled by the attacker. The environment variables often contain sensitive credentials such as CI/CD tokens, cloud service keys, and database secrets, leading to a severe information leak. The package also exposes unrelated wallet functions, indicating it is a lure rather than a genuine Docker client. No patch or fix is currently documented for this malicious package.
AI Analysis
Technical Summary
[email protected] is a malicious npm package designed to masquerade as a Docker API client but instead performs credential theft. Upon being imported, it gathers detailed system and environment data, including sensitive credentials commonly found in environment variables. This information is encoded and sent to an attacker-controlled Telegram chat via a hardcoded bot token and chat ID. The presence of wallet-related functions unrelated to Docker confirms the package's deceptive nature. This represents a supply chain compromise risk through typosquatting, where developers mistakenly install this package instead of the legitimate dockerode client.
Potential Impact
Any process that imports [email protected] leaks its full environment, including sensitive credentials such as AWS keys, GitHub tokens, NPM tokens, and database secrets, to an attacker-controlled Telegram chat. This can lead to unauthorized access to cloud services, source code repositories, package registries, and databases, severely compromising the security of affected systems and organizations.
Mitigation Recommendations
No official patch or remediation is available for this malicious package. The recommended mitigation is to avoid installing or using [email protected] and instead use the legitimate dockerode package. Developers and organizations should audit their dependencies for typosquatting and malicious packages, remove docker-api-client if present, and rotate any potentially exposed credentials. Monitoring package sources and using trusted package registries with supply chain security measures can help prevent such incidents.
Malicious code in docker-api-client (npm)
Description
The npm package [email protected] is a malicious typosquat of the legitimate dockerode package. When required, it collects extensive environment information including hostname, username, home directory, platform, current working directory, and the entire process environment variables. This data is serialized, encoded, and exfiltrated via HTTPS GET requests to a Telegram bot controlled by the attacker. The environment variables often contain sensitive credentials such as CI/CD tokens, cloud service keys, and database secrets, leading to a severe information leak. The package also exposes unrelated wallet functions, indicating it is a lure rather than a genuine Docker client. No patch or fix is currently documented for this malicious package.
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
[email protected] is a malicious npm package designed to masquerade as a Docker API client but instead performs credential theft. Upon being imported, it gathers detailed system and environment data, including sensitive credentials commonly found in environment variables. This information is encoded and sent to an attacker-controlled Telegram chat via a hardcoded bot token and chat ID. The presence of wallet-related functions unrelated to Docker confirms the package's deceptive nature. This represents a supply chain compromise risk through typosquatting, where developers mistakenly install this package instead of the legitimate dockerode client.
Potential Impact
Any process that imports [email protected] leaks its full environment, including sensitive credentials such as AWS keys, GitHub tokens, NPM tokens, and database secrets, to an attacker-controlled Telegram chat. This can lead to unauthorized access to cloud services, source code repositories, package registries, and databases, severely compromising the security of affected systems and organizations.
Defensive Guidance
No official patch or remediation is available for this malicious package. The recommended mitigation is to avoid installing or using [email protected] and instead use the legitimate dockerode package. Developers and organizations should audit their dependencies for typosquatting and malicious packages, remove docker-api-client if present, and rotate any potentially exposed credentials. Monitoring package sources and using trusted package registries with supply chain security measures can help prevent such incidents.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-13280
- Osv Schema Version
- 1.7.4
- Ecosystems
- ["npm"]
Threat ID: 6a738521bf8831d5394efa21
Added to database: 08/05/2026, 18:46:57 UTC
Last enriched: 08/05/2026, 22:17:38 UTC
Last updated: 09/07/2026, 22:04:11 UTC
Views: 21
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.