registry / @socketsecurity/cli / 1.2.0
@socketsecurity/cli@1.2.0
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe inspected metadata and launcher show user-invoked CLI execution and no lifecycle hook. The required binary JAR cannot be source-validated, so a clean verdict cannot be grounded for the complete required path set.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
User invocation of a declared command-line entrypoint.
Impact
No malicious impact was confirmed by the inspected source.
Mechanism
The wrapper starts the bundled CLI and forwards command-line arguments.
AI rationale
The inspected metadata and launcher show user-invoked CLI execution and no lifecycle hook. The required binary JAR cannot be source-validated, so a clean verdict cannot be grounded for the complete required path set.
Decision evidence
public snapshotAI called this Manual Review at 72.0% confidence as Unknown with medium false-positive risk.
AI review observations
- Package metadata defines command-line entrypoints rather than an install lifecycle hook.
- The primary wrapper launches the bundled CLI with caller-supplied arguments.
- A required Maven-extension JAR is binary and has no inspectable UTF-8 source excerpt, preventing complete source validation.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
17 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
external/blessed/lib/tput.jsView file
1152if (this.options.stringify && code.indexOf('return ') === 0) {
L1153: return new Function('', code)();
L1154: }
High
Eval
Package source references dynamic code evaluation.
external/blessed/lib/tput.jsView on unpkg · L1152bin/npm-cli.jsView file
4void (async () => {
L5: const Module = require('node:module')
L6: const path = require('node:path')
Findings
2 Critical9 High8 Medium6 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilitydist/vendor.js
HighChild Processbin/cli.js
HighShell
HighEvalexternal/blessed/lib/tput.js
HighCommand Output Exfiltrationdist/vendor.js
HighCross File Remote Execution Contextdist/cli.js
HighTrigger Reachable Credential Exfiltrationdist/vendor.js
HighTrigger Reachable Persistencedist/cli.js
HighShips High Entropy Blobdist/manifest-scripts/maven-extension/coana-maven-extension.jar
HighSemantic Analysis Limiteddist/vendor.js
Medium
Affected versions and remediation
This report applies to @socketsecurity/cli@1.2.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.2.0 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.