mano-coding@0.1.50
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe bundled resolver has a concrete credential disclosure path: it propagates an npm authorization header to a tarball URL supplied by registry metadata without checking the destination host. This is triggered by a user-run package-resolution operation, not by installation or ordinary import.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs a CLI operation that resolves a direct npm package while an npm token is available.
Impact
A registry response with a foreign tarball URL can disclose the user's npm token to that host.
Mechanism
The resolver applies a general npm environment token to the metadata request, carries its authorization header into release data alongside the metadata-provided tarball URL, then sends that header when downloading the tarball without checking that the URL host matches the registry.
Attack narrative
When a user resolves a direct npm package, the CLI can obtain an npm token from the environment and send it to the configured registry. It then trusts the registry response's tarball URL, carries the same authorization header into the release record, and sends that header to the tarball host. A malicious or compromised metadata source can therefore direct the user's npm token to a foreign host.
AI rationale
The bundled resolver has a concrete credential disclosure path: it propagates an npm authorization header to a tarball URL supplied by registry metadata without checking the destination host. This is triggered by a user-run package-resolution operation, not by installation or ordinary import.
Evidence
dist/bin.jsbin/mano-coding.js
Network endpoints2
registry.npmjs.org (default registry)Host specified by registry metadata's dist.tarball URL
Decision evidence
public snapshotAI called this Malicious at 95.0% confidence as Malware with low false-positive risk.
Evidence for block
- The npm authorization resolver falls back to NPM_TOKEN, NPM_AUTH_TOKEN, or MANO_NPM_AUTH_TOKEN without restricting the token to a host.
- The direct npm resolver accepts the tarball URL from registry metadata and copies the metadata request's authorization header into release sources.
- The tarball downloader sends that stored authorization header to the tarball URL.
- The CLI launcher imports the bundled command-line program when invoked.
Evidence against
- The package has no install lifecycle scripts.
- Network access and npm credential handling fit the package's CLI and package-resolution purpose when they stay with the configured registry.
- The flagged Mozilla and other foreign host strings were not shown to be credential destinations.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
Source & flagged code
7 flaggeddist/bin.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = mano-coding@0.1.47
matchedIdentity = npm:bWFuby1jb2Rpbmc:0.1.47
similarity = 0.500
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/bin.jsView on unpkg1159var EventEmitter = __require("node:events").EventEmitter;
L1160: var childProcess = __require("node:child_process");
L1161: var path3 = __require("node:path");
High
1999}
L2000: const execArgv = process4.execArgv ?? [];
L2001: if (execArgv.includes("-e") || execArgv.includes("--eval") || execArgv.includes("-p") || execArgv.includes("--print")) {
High
Findings
1 Critical4 High3 Medium6 Low
CriticalPrevious Version Dangerous Deltadist/bin.js
HighChild Processdist/bin.js
HighShelldist/bin.js
HighSame File Env Network Executiondist/bin.js
HighCommand Output Exfiltrationdist/bin.js
MediumDynamic Requirebin/mano-coding.js
MediumNetwork
MediumEnvironment Vars
LowScripts Present
LowEvaldist/bin.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
Affected versions and remediation
This report applies to mano-coding@0.1.50.
See all versions of mano-coding for other recorded verdicts.
- Avoid installing mano-coding@0.1.50. 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: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.