@wethenorth12/crypto-config
This report shows the evidence for @wethenorth12/crypto-config@2.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12089 confirms this npm version as malicious.
Advisory
MAL-2026-12089
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/crypto-config (npm)
Details
On require, index.js collects process.env, hostname, username, homedir, platform, and cwd, base64-encodes the blob, and POSTs it to api.telegram.org/bot<token>/sendMessage with a hardcoded bot token and chat_id 8969499041. A tmp marker file gates repeat sends. The package presents itself as a drop-in for the popular `config` package (typosquat), attempts to require('config') and re-exports it to preserve apparent functionality, and uses randomized variable names to obscure the exfiltration path.
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/crypto-config@2.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wethenorth12/crypto-config@2.0.1. 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.