@wagni_bot/eth-agent
This report shows the evidence for @wagni_bot/eth-agent@1.1.2. 9 of 9 known versions are blocked or flagged. See all versions.
OpenSSF/OSV Malicious Advisory
imported 3mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-10024 confirms this npm version as malicious.
Advisory
MAL-2026-10024
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in @wagni_bot/eth-agent (npm)
Details
The npm package `@wagni_bot/eth-agent` is a supply-chain credential stealer disguised as a **Ethereum** SDK. It is one member of a coordinated campaign of 25 crypto/web3 typosquat packages published under the single npm scope `@wagni_bot` on 2026-07-09.
Each package declares a `postinstall` lifecycle hook (`postinstall: node postinstall.js`) that executes automatically on `npm install`, before the package is ever imported. The script fingerprints the host and user (`os.hostname()`, `os.userInfo()`, `os.platform()`), walks the user's home directory (`readdirSync`/`readFileSync`) and reads high-value secrets — SSH private keys (`~/.ssh/id_rsa`), cryptocurrency wallet files, and `.env` files (API keys, tokens, seed phrases). It then JSON-encodes the collected data and exfiltrates it to a hardcoded Telegram bot via the Telegram Bot API `sendMessage` endpoint (https://api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage). All error paths are swallowed so the install appears normal.
codelake Research proved the packages belong to one campaign deterministically: the payload file is byte-identical across all 25 packages at each published version (version-lockstep), and every package exfiltrates to the same Telegram bot token — a single automated actor. Detected and classified independently from the live npm feed on 2026-07-09; at the time of reporting the packages were still live on npm and none of the 25 were present in OSV or GHSA (a first-catch).
---
## Source: amazon-inspector (08c234c984ea87a7d4c780dc8ddbc244926628e405ea0f7ac9798309260a6122) The package advertises itself as an 'Unofficial eth-agent SDK' but ships an empty main module (index.js contains only `module.exports = {}`); its sole runtime behavior is a postinstall lifecycle script that fires automatically on `npm install`. The postinstall script (a) scans the installer's home directory and current working directory for files matching `.pem`, `.key`, `id_rsa`, `id_ed25519`, `.cred`, and `.env`, (b) walks `~/.ssh` to collect SSH private keys, (c) iterates `process.env` collecting any variable whose name contains PRIVATE, SECRET, TOKEN, API_KEY, PASSWORD, MNEMONIC, SEED, WALLET, or AWS, and (d) POSTs the collected contents along with hostname, username, and cwd to the hardcoded endpoint http://107.161.90.180:7777 over plain HTTP with no TLS and no authentication. Errors are silently swallowed. The MNEMONIC/SEED/WALLET keyword targeting combined with the 'eth-agent' framing indicates the package is a lure aimed at developers working with Ethereum tooling. Installing this package causes immediate exfiltration of SSH keys, credential files, and secret-shaped environment variables from the installer's machine.
Independent LPM AI assessment
CleanIndependent AI assessment: clean. LPM AI assessed this version as clean; the assessments disagree.
Static inspection found an install-time hook, but the referenced postinstall.js is not present and the only runtime entrypoint is an empty export. With no payload, network, credential access, filesystem mutation, or agent control-surface writes, the scanner lifecycle finding is not enough to mark malicious.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install lifecycle postinstall
Impact
No malicious payload confirmed; likely install failure or broken package behavior.
Mechanism
missing lifecycle script target
AI rationale
Static inspection found an install-time hook, but the referenced postinstall.js is not present and the only runtime entrypoint is an empty export. With no payload, network, credential access, filesystem mutation, or agent control-surface writes, the scanner lifecycle finding is not enough to mark malicious.
Evidence
package.jsonindex.js
Independent scan evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json defines postinstall: node postinstall.js
- postinstall.js is referenced but absent from extracted package
Evidence against
- Only package files present are package.json and index.js
- index.js contains only module.exports={}
- No credential/env/file harvesting found
- No network endpoints found
- No child_process/eval/dynamic loading/native binary code found
- No AI-agent config or control-surface writes found
Behavioral surface
Trivial
NoLicense
Source & flagged code
2 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node postinstall.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node postinstall.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
1 High1 Medium2 Low
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
LowScripts Present
LowNo License
Affected versions and remediation
This report applies to @wagni_bot/eth-agent@1.1.2.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/eth-agent@1.1.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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.