socket@1.1.176
CLI for Socket.dev
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found a normal user-invoked CLI with no install lifecycle hook. The flagged evaluation and bundled code do not establish an active malicious data-flow or payload.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a Socket CLI command, including an explicit login command.
Impact
No unconsented install-time execution, credential harvesting, persistence, or destructive action was found.
Mechanism
Local CLI execution and optional API-client communication.
AI rationale
Static inspection found a normal user-invoked CLI with no install lifecycle hook. The flagged evaluation and bundled code do not establish an active malicious data-flow or payload.
Network endpoints1
api.socket.dev
Decision evidence
public snapshotAI called this Clean at 85.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest contains development build scripts and no npm preinstall, install, or postinstall hook.
- The bin launcher only starts the package's local bundled CLI with the user's command-line arguments.
- The flagged dynamic Function use is terminal capability formatting in blessed, not install-time or remote payload execution.
- The flagged registry file is a bundled implementation importing standard Node modules; inspection found no credential-send path tied to this package entrypoint.
- The runtime bundles local CLI and vendor modules; its login flow explicitly prompts for an API token and stores user-provided endpoint settings.
- The Maven artifact contains a Java archive manifest marker, but no npm lifecycle path executes it.
Evidence against
- The CLI supports user-configurable API endpoint and proxy settings, so network requests can occur during explicit CLI use.
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')
Medium
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 socket@1.1.176.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.176 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.