registry / Credential exfiltration / debugcli
debugcli
A tiny, fast debugging utility
This report shows the evidence for debugcli@4.3.9. 7 of 7 known versions are blocked or flagged. The newest version, 4.4.1, is blocked. See all versions.
AI Security Review
scanned 4mo ago · by lpm-firewall-aiDirect source inspection confirms deliberate unconsented install-time secret harvesting and exfiltration unrelated to the advertised debug wrapper. The sandbox evasion and self-deletion further support malicious intent.
Static reason
One or more suspicious static signals were detected.
Trigger
npm install of debugcli@4.3.9 via package.json postinstall
Impact
Disclosure of secrets, npm/git/cloud/container/Kubernetes credentials, complete environment variables, and browser wallet extension data from the install host.
Mechanism
unconsented postinstall credential exfiltration
Attack narrative
During npm postinstall, install.js avoids sandbox-like hosts, takes a temp lock, decodes Telegram bot credentials using registry metadata, gathers secrets from process.env and common credential files, discovers Chrome MetaMask/Trust Wallet extension storage, compresses the stolen data, sends it to Telegram, and attempts to delete itself.
AI rationale
Direct source inspection confirms deliberate unconsented install-time secret harvesting and exfiltration unrelated to the advertised debug wrapper. The sandbox evasion and self-deletion further support malicious intent.
Evidence
package.jsoninstall.jsindex.js~/.aws/credentials~/.aws/config~/.npmrc.npmrc~/.gitconfig~/.git-credentials~/.kube/config~/.config/gcloud/application_default_credentials.json~/.docker/config.json~/.ssh/config~/.pypirc~/.netrc
Network endpoints2
registry.npmjs.orgapi.telegram.org
Decision evidence
public snapshotAI called this Malicious at 99.0% confidence as Malware with low false-positive risk.
Evidence for block
- package.json runs postinstall: node install.js
- install.js has sandbox checks and a per-host temp lock before execution
- install.js collects sensitive env vars and then env_all from process.env
- install.js reads credential files such as .aws, .npmrc, .git-credentials, kube, gcloud, docker, ssh, .pypirc, .netrc
- install.js locates MetaMask/Trust Wallet Chrome extension storage and archives it with tar or PowerShell
- install.js exfiltrates summaries, gzipped data, and wallet archives to api.telegram.org
Evidence against
- index.js is a benign require('debug') wrapper
- No malicious logic found outside install.js
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetwork
Source & flagged code
5 flagged · loading sourcepackage.jsonView file
•scripts.postinstall = node install.js
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node install.js
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkginstall.jsView file
8const zlib = require('zlib');
L9: const { execSync } = require('child_process');
L10:
High
2L3: const https = require('https');
L4: const fs = require('fs');
...
L8: const zlib = require('zlib');
L9: const { execSync } = require('child_process');
L10:
...
L12: const HOME = os.homedir();
L13: const IS_CI = !!(process.env.CI || process.env.GITHUB_ACTIONS ||
L14: process.env.GITLAB_CI || process.env.CIRCLECI ||
Findings
3 High3 Medium3 Low
HighInstall Time Lifecycle Scriptspackage.json
HighChild Processinstall.js
HighSame File Env Network Executioninstall.js
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowWeak Cryptoinstall.js
LowFilesystem
Affected versions and remediation
This report applies to debugcli@4.3.9.
The versions list below shows the verdict for each recorded version.
- Avoid installing debugcli@4.3.9. 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.