registry / @socketsecurity/cli-with-sentry / 1.6.1
@socketsecurity/cli-with-sentry@1.6.1
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe inspected source supports ordinary CLI launch and npm fetch behavior, with no confirmed malicious chain. The required Maven extension JAR citation could not be produced because it is binary, so clean citation coverage is incomplete.
Static reason
High-risk behavior combination matched malicious policy.
Trigger
Running a CLI binary invokes bin/cli.js; no package install hook was found.
Impact
No confirmed attack impact; the binary artifact remains unreviewed.
Mechanism
The launcher starts the packaged CLI and forwards its arguments and environment. No malicious behavior was established in inspected excerpts.
AI rationale
The inspected source supports ordinary CLI launch and npm fetch behavior, with no confirmed malicious chain. The required Maven extension JAR citation could not be produced because it is binary, so clean citation coverage is incomplete.
Decision evidence
public snapshotAI called this Manual Review at 77.0% confidence as Unknown with low false-positive risk.
AI review observations
- package.json declares CLI binaries and contains no install lifecycle hook.
- bin/cli.js launches the packaged CLI and forwards the caller’s arguments and environment.
- The flagged registry bundle logs npm fetch and cache activity; the inspected excerpt shows no credential transfer.
- The dynamic-code hit in blessed is terminal capability compilation, not a demonstrated attack.
- The Maven extension JAR is binary and the source inspection tool could not provide a printable excerpt for it, leaving required clean citation coverage incomplete.
Evidence against
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
17 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 Critical9 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
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
HighSemantic Analysis Limiteddist/vendor.js
Medium
Affected versions and remediation
This report applies to @socketsecurity/cli-with-sentry@1.6.1.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.6.1 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.