registry / @socketsecurity/cli / 1.10.0
@socketsecurity/cli@1.10.0
⚠ Under reviewCLI for Socket.dev
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source does not establish malicious behavior, but the bundled Maven extension has executable classes whose behavior remains unresolved. Manual review is appropriate for that unresolved runtime behavior.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user invokes Maven manifest analysis through the CLI.
Impact
The extension's effects during Maven analysis cannot be determined from the inspected source.
Mechanism
The CLI adds the bundled extension archive to Maven's extension class path; the available archive analysis does not resolve the behavior of several executable classes.
AI rationale
The inspected source does not establish malicious behavior, but the bundled Maven extension has executable classes whose behavior remains unresolved. Manual review is appropriate for that unresolved runtime behavior.
Evidence
dist/cli.js.lpm-inspection-wNK74K/0-9ac074e1c718.txt
Decision evidence
public snapshotAI called this Manual Review at 79.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest maps command names to bin launchers; its scripts section contains build and check tasks, not an install hook.
- The bundled token helper requires GitHub Actions token variables and builds the request URL from the Actions-provided URL.
- The Maven command attaches the bundled extension to Maven when the user invokes Maven analysis.
- The offline archive analysis identifies binary extension classes whose behavior requires caller and context inspection.
Evidence against
- The inspected token helper requests an identity token using the Actions-provided endpoint; the inspected excerpt does not show an unrelated recipient.
- The Maven extension is activated through a user-invoked Maven analysis command.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
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.0.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.10.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.