socket@1.1.154
CLI for Socket.dev
AI Security Review
scanned 3mo ago · by lpm-firewall-aiThe flagged primitives implement an explicitly invoked Socket security CLI, including normal authenticated API requests and an npm risk-check wrapper. No lifecycle execution, credential harvesting to an unrelated endpoint, stealth persistence, or remote payload chain was found.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
User runs `socket`, `socket-npm`, or another package bin command.
Impact
Expected package-analysis data and configured Socket API credentials may be sent to the Socket API during requested commands.
Mechanism
Explicit CLI security scanning and npm-wrapper alert lookup.
AI rationale
The flagged primitives implement an explicitly invoked Socket security CLI, including normal authenticated API requests and an npm risk-check wrapper. No lifecycle execution, credential harvesting to an unrelated endpoint, stealth persistence, or remote payload chain was found.
Evidence
package.jsonbin/cli.jsdist/shadow-npm-bin2.jsdist/shadow-npm-inject.jsdist/cli.jsdist/utils.jsbin/npm-cli.jsdist/constants.jsexternal/@socketsecurity/registry/external/libnpmpack.js
Network endpoints1
api.socket.dev/v0/
Decision evidence
public snapshotAI called this Clean at 94.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- User-invoked CLI sends package metadata to Socket API for security alerts.
- `socket-npm` injects a guarded Arborist wrapper when explicitly run.
Evidence against
- `package.json` has no preinstall/install/postinstall hooks.
- `bin/cli.js` only launches the bundled CLI after a user invokes a bin command.
- `dist/shadow-npm-bin2.js` activates npm wrapping only through explicit socket-npm/npx commands.
- `dist/shadow-npm-inject.js` performs alert checks before delegating to npm; no hidden payload execution found.
- API token persistence occurs only in explicit `socket login`/config flows.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsObfuscatedUrlStrings
Source & flagged code
14 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
2 Critical6 High8 Medium7 Low
CriticalCredential Exfiltrationexternal/@socketsecurity/registry/external/libnpmpack.js
CriticalPrevious Version Dangerous Deltaexternal/@socketsecurity/registry/external/libnpmpack.js
HighChild Processbin/cli.js
HighShell
HighEvalexternal/blessed/lib/tput.js
HighCross File Remote Execution Contextdist/cli.js
HighTrigger Reachable Persistencedist/cli.js
HighShips High Entropy Blobdist/manifest-scripts/maven-extension/coana-maven-extension.jar
MediumDynamic Requirebin/npm-cli.js
MediumNetwork
MediumEnvironment Vars
MediumInstall Persistencedist/cli.js
Affected versions and remediation
This report applies to socket@1.1.154.
See all versions of socket for other recorded verdicts.
- Review the evidence and your use of socket@1.1.154 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.