registry / Credential exfiltration / @wagni_bot/opensea-sdk
@wagni_bot/opensea-sdk
Unofficial opensea-sdk SDK
This report shows the evidence for @wagni_bot/opensea-sdk@1.0.0. 9 of 9 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 and file harvesting with external exfiltration to Telegram, unrelated to an OpenSea SDK. This is concrete malicious behavior and should be blocked.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
npm install runs package.json postinstall
Impact
Exposure of environment secrets, SSH keys/config, .env files, wallet/seed material, API tokens, passwords, AWS credentials, and host/user metadata
Mechanism
install-time credential and sensitive file exfiltration
Attack narrative
On installation, npm runs postinstall.js. The script reports host metadata to a Telegram bot, scans the current project, the user's home directory, and ~/.ssh for secret-like filenames, reads file contents, filters sensitive environment variables, and posts collected data to Telegram. The package's main entrypoint has no real SDK behavior.
AI rationale
Direct source inspection confirms unconsented install-time credential and file harvesting with external exfiltration to Telegram, unrelated to an OpenSea SDK. This is concrete malicious behavior and should be blocked.
Evidence
package.jsonpostinstall.jsindex.jsprocess.cwd() secret-like filesos.homedir() secret-like files~/.ssh/id_rsa~/.ssh/id_ed25519~/.ssh/config
Network endpoints1
api.telegram.org/bot<hardcoded-token>/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 and chat id
- postinstall.js sends host/user/cwd/platform on install to api.telegram.org
- postinstall.js scans process.cwd(), os.homedir(), and ~/.ssh for .env, key, wallet, seed, secret-like files
- postinstall.js reads matching files and sends contents in chunks
- postinstall.js filters process.env for PRIVATE/SECRET/TOKEN/API_KEY/PASSWORD/MNEMONIC/SEED/WALLET/AWS and sends matches
Evidence against
- index.js only exports an empty object
- No benign SDK functionality 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/opensea-sdk@1.0.0.
The versions list below shows the verdict for each recorded version.
- Avoid installing @wagni_bot/opensea-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.