registry / @socketsecurity/cli / 1.10.1
@socketsecurity/cli@1.10.1
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe inspected source does not establish malicious behavior, and the package has no install lifecycle hook. Manual review is warranted because the bundled Maven extension is executable and its class behavior remains unresolved.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes the CLI’s Maven analysis path.
Impact
The extension runs within Maven during analysis, but its effects could not be determined from the available inspection.
Mechanism
The CLI adds the bundled extension JAR to Maven’s extension class path and runs Maven validation; the extension bytecode’s behavior remains unresolved.
AI rationale
The inspected source does not establish malicious behavior, and the package has no install lifecycle hook. Manual review is warranted because the bundled Maven extension is executable and its class behavior remains unresolved.
Evidence
dist/cli.js.lpm-inspection-Qiwq7i/0-c5c49864f369.txtdist/manifest-scripts/maven-extension/coana-maven-extension.jar
Decision evidence
public snapshotAI called this Manual Review at 89.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes CLI commands and lists build scripts; it has no preinstall, install, or postinstall hook.
- The Maven scan path loads the bundled extension through Maven’s extension class path.
- The offline artifact analysis reports executable class files whose behavior requires caller and context inspection; their implementation remains unresolved.
Evidence against
- The launcher starts the bundled CLI as a child process, and the unresolved extension is reached through the Maven analysis path.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
18 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
3 Critical9 High8 Medium6 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalTrigger Reachable Dangerous Capabilitydist/vendor.js
CriticalPrevious Version Dangerous Deltadist/cli.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
Affected versions and remediation
This report applies to @socketsecurity/cli@1.10.1.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.10.1 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.