@socketsecurity/cli@1.1.169
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install hook, exfiltration path, persistence, or destructive action was established. The opaque Java archive combined with runtime execution and network capabilities warrants a warning rather than a clean verdict.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
A user runs one of the package's CLI binaries or a command that invokes its Maven extension.
Impact
The archive and its possible Maven-extension behavior cannot be verified from inspectable source, so its runtime capabilities remain unresolved.
Mechanism
Runtime process spawning, API-client calls, and an opaque bundled archive.
AI rationale
No concrete malicious install hook, exfiltration path, persistence, or destructive action was established. The opaque Java archive combined with runtime execution and network capabilities warrants a warning rather than a clean verdict.
Evidence
bin/cli.jsdist/cli.jsdist/vendor.jsdist/manifest-scripts/maven-extension/coana-maven-extension.jar
Network endpoints1
api.socket.dev/v0
Decision evidence
public snapshotAI called this Suspicious at 72.0% confidence as Unknown with medium false-positive risk.
Evidence for warning
- The package ships an opaque Java archive that static source review cannot meaningfully assess.
- Its executable launcher spawns a separate Node process with the caller's environment.
- The bundled CLI imports process-spawning and file-system APIs and makes SDK API calls at command runtime.
- A bundled terminal library dynamically compiles generated code with Function.
- The bundled vendor code defines a Socket API endpoint for runtime requests.
Evidence against
- package.json defines bin entrypoints but no preinstall, install, or postinstall lifecycle hook.
- The launcher activity is reached through an explicit CLI command, not package installation.
- The inspected libnpmpack file is bundled package-management code; its network imports alone do not establish credential exfiltration.
- No self-dependency or automatic project-wide mutation was found in the manifest.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystem
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
2 Critical10 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
HighCredential Redirect Persistencedist/vendor.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.1.169.
See all versions of @socketsecurity/cli for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli@1.1.169 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.