@wethenorth12/docker-api-client
This report shows the evidence for @wethenorth12/docker-api-client@2.0.2, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12090 confirms this npm version as malicious.
Advisory
MAL-2026-12090
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/docker-api-client (npm)
Details
Package advertises itself as a 'drop-in replacement for dockerode' but the main module (index.js) has no Docker functionality. On require, it collects hostname, username, home directory, platform, cwd, a timestamp, and the entire process.env, base64-encodes a JSON blob of those fields, and sends it via an HTTPS GET to api.telegram.org/bot<token>/sendMessage with chat_id=8969499041. A tmp marker file suppresses repeat sends. The wholesale process.env dump routinely carries CI/build secrets such as AWS_*, GITHUB_TOKEN, NPM_TOKEN, and other installer-owned credentials, so the beacon functions as a credential harvester. The fallback module.exports exposes unrelated crypto/wallet stubs (createWallet, generateMnemonic returning random bytes, signTransaction) and attempts to re-export dockerode if present, serving as cover for the exfiltration.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to @wethenorth12/docker-api-client@2.0.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wethenorth12/docker-api-client@2.0.2. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.