socket@1.10.0
CLI for Socket.dev
AI Security Review
scanned 14d ago · by lpm-firewall-aiThe inspected source supports a clean verdict: the credential-related scanner match is archive metadata handling, and the flagged dynamic code is terminal capability processing. No install hook or concrete attack behavior was found; the Maven extension is used by explicit CLI integration commands.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A user runs a Socket CLI command; Maven integration runs only when the relevant facts or workspace command invokes it.
Impact
No malicious credential transfer, persistence, destructive action, or unconsented install-time behavior was established.
Mechanism
The package launcher starts its CLI. The npm archive helper records the local user name as archive metadata, while the terminal library constructs functions for terminal capabilities.
AI rationale
The inspected source supports a clean verdict: the credential-related scanner match is archive metadata handling, and the flagged dynamic code is terminal capability processing. No install hook or concrete attack behavior was found; the Maven extension is used by explicit CLI integration commands.
Decision evidence
public snapshotAI called this Clean at 90.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- package.json exposes CLI commands and has no install lifecycle hook; its scripts are build and development tasks.
- The launcher runs the packaged CLI, whose Maven extension is invoked by explicit facts or workspace commands.
- The flagged environment-variable match in the npm packer supplies user metadata for archive entries.
- The flagged dynamic code construction is in terminal capability handling; no attack behavior was established from it.
- The flagged dependency and archive files are bundled tooling or an explicitly invoked Maven integration; inspection did not establish malicious behavior.
Evidence against
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')
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.10.0.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@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.