@wethenorth12/web3-provider-engine
This report shows the evidence for @wethenorth12/web3-provider-engine@16.0.5, the only known version.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-12106 confirms this npm version as malicious.
Advisory
MAL-2026-12106
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wethenorth12/web3-provider-engine (npm)
Details
Package name mimics MetaMask's official web3-provider-engine and its README advertises a drop-in replacement, but the exported API (connect/createWallet/generateMnemonic) is a hollow stub — generateMnemonic returns crypto.randomBytes(32).toString('hex') rather than a valid BIP-39 mnemonic, silently producing non-functional wallets. On module load via the declared main (index.js), the package reads the entire process.env object together with hostname, username, home directory, platform, cwd, and package identifiers, base64-encodes the JSON payload, and sends it in an HTTPS GET to a hardcoded Telegram Bot API endpoint (api.telegram.org, bot ID 7231970337, chat_id 8969499041). A marker file (.npi-<random>) in the OS temp directory suppresses repeat sends per host. Bulk enumeration of process.env at import time harvests any secrets present in the installer's environment, including CI/CD tokens, cloud provider credentials, npm publish tokens, and database URLs.
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/web3-provider-engine@16.0.5.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wethenorth12/web3-provider-engine@16.0.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.