auto-debug-tool
Does something useful like string formatting
This report shows the evidence for auto-debug-tool@1.0.3. 3 of 4 known versions are blocked or flagged. The newest version, 0.0.1-security, is allowed. See all versions.
AI Security Review
scanned 3mo ago · by lpm-firewall-aiDirect source inspection confirms an unconsented install-time remote executable download and hidden execution chain. This is concrete malware behavior, not a package-aligned setup action.
Decision evidence
public snapshot- `package.json` runs `node install.js` on `postinstall`.
- `install.js` targets Windows non-development installs.
- `install.js` downloads an EXE from GitHub and launches it hidden.
- `install.js` invokes PowerShell with execution-policy bypass.
- `README.md` describes an npm-install stager and process hollowing.
- `index.js` only exports simple string and sleep utilities.
- No benign purpose justifies the hidden install-time executable download.
Source & flagged code
4 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgSource gates dangerous network, credential, or execution behavior behind CI, host, platform, time, or geo fingerprint checks.
Findings
Affected versions and remediation
This report applies to auto-debug-tool@1.0.3.
The versions list below shows the verdict for each recorded version.
- Avoid installing auto-debug-tool@1.0.3. 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.