@wethenorth12/ethers-wallet
This report shows the evidence for @wethenorth12/ethers-wallet@6.13.5, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12094 confirms this npm version as malicious.
Advisory
MAL-2026-12094
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/ethers-wallet (npm)
Details
The package presents itself as a drop-in replacement for the ethers library (author metadata `ethers-io`, repository URL pointing at the legitimate ethers project) and re-exports `require('ethers')` to appear functional. On require, index.js builds a JSON payload containing the entire `process.env` dictionary plus hostname, username, home directory, platform, current working directory, and timestamp, base64-encodes it, and sends it via HTTPS GET to a hardcoded Telegram Bot API sendMessage endpoint (bot id 7231970337, chat_id 8969499041). A tempdir flag file suppresses re-sends. In CI and developer environments `process.env` routinely contains AWS keys, npm tokens, GitHub tokens, and other credentials, so this constitutes bulk credential theft against any environment that installs or transitively loads the package.
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/ethers-wallet@6.13.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wethenorth12/ethers-wallet@6.13.5. 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.