Which versions of docker-api-client are malicious?

The following npm versions of docker-api-client are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate docker-api-client if I installed it?

docker-api-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed docker-api-client — how do I know if it already compromised me?

If docker-api-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is docker-api-client part of a known attack campaign?

Yes — docker-api-client is associated with the IN-MAL-2026-015740 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find docker-api-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for docker-api-client (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging docker-api-client across your stack and pipelines.

Malicious package

docker-api-clientnpm

docker-api-client is a confirmed malicious npm package (MAL-2026-13280) that steals credentials and exfiltrates sensitive data (malicious version 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in docker-api-client (npm)

MAL-2026-13280

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall docker-api-client

What this malware does

[email protected] is a typosquat of dockerode. On require(), index.js collects hostname, username, homedir, platform, cwd, and the entire process.env object, JSON-serializes and base64-encodes the payload, and sends it via HTTPS GET to api.telegram.org bot sendMessage with a hardcoded bot token and chat_id; a tmp flag file marks first-run. The environment dump routinely contains CI/CD tokens, cloud credentials (AWS_*, GITHUB_TOKEN, NPM_TOKEN), and database secrets, so any process that imports this package leaks its full credential-bearing environment to an attacker-controlled Telegram chat. The module's fallback exports expose wallet primitives (createWallet, signTransaction, generateMnemonic) that do not match the advertised Docker API purpose, confirming the package as a cover-story lure rather than a Docker client.

Malicious versions

1 flagged

2.0.2

Indicators of compromise (SHA-256)

f02e61d324161238593fb7e59dc907f183bf885a908354fed1eba0662906947b

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for docker-api-client (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging docker-api-client across your stack and pipelines.
If you installed it — respond
docker-api-client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If docker-api-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks docker-api-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. docker-api-client on npm has been identified as a malicious package (version 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-015740

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks docker-api-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database