mano-coding@0.1.57
Mano Coding CLI and toolchain
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe bundle reuses an npm authorization header for a tarball URL supplied by registry metadata without an apparent host check. This is a credential-handling risk in a user-invoked resolver, so it warrants a warning rather than a malicious verdict.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user invokes a command that resolves a package, and the registry metadata provides a tarball URL on another host.
Impact
An untrusted or compromised registry response could cause an npm token to be disclosed to a foreign tarball server.
Mechanism
The resolver obtains authorization for the metadata request, stores it with the release source, then reuses it in the tarball request without an apparent destination-host check.
AI rationale
The bundle reuses an npm authorization header for a tarball URL supplied by registry metadata without an apparent host check. This is a credential-handling risk in a user-invoked resolver, so it warrants a warning rather than a malicious verdict.
Evidence
dist/bin.js
Network endpoints2
registry.npmjs.org/Configured registry URL (source.registry); metadata-provided tarballUrl
Decision evidence
public snapshotAI called this Suspicious at 87.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The resolver can use NPM_TOKEN or NPM_AUTH_TOKEN as authorization when resolving a package.
- It carries the authorization header used for registry metadata into the release source alongside the metadata-provided tarball URL.
- The tarball download sends that carried header to tarballUrl without a visible check that its host matches the registry host.
Evidence against
- The credential flow is in dependency resolution and requires a resolver command and metadata that supplies a tarball URL.
- The npmrc credential lookup matches configured credentials to the request host; the identified risk is the generic environment-token fallback and subsequent forwarding.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
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.57.
See all versions of mano-coding for other recorded verdicts.
- Review the evidence and your use of mano-coding@0.1.57 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.