Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Malicious code in @wagni_bot/eth-agent (npm)

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

osv · MAL-2026-10024

Published

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). --- _-= Per source details. Do not edit below this line.=-_ ## 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.

Source published
9 Jul 2026 00:00:00 UTC
Source modified
1 Sep 2026 11:30:33 UTC
Saved here
24 Oct 2026 13:17:17 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 20 Nov 02:35 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current