registry / @socketsecurity/cli-with-sentry / 1.1.160
@socketsecurity/cli-with-sentry@1.1.160
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 1mo ago · by lpm-firewall-aiInspected JavaScript has no install hook and loads the Maven jar only from a user-invoked CLI path. That jar is non-UTF8 and unreadable, so its behavior cannot be cleared or shown to be an attack.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
A person runs a package bin command that later calls invokeMaven. Package install itself has no script hook.
Impact
No confirmed install mutation, credential theft, or remote payload was established. Maven-extension behavior remains unverified because the jar is opaque.
Mechanism
invokeMaven supplies the local jar to Maven through maven.ext.class.path. The jar file refused text reads, so its classes were not reviewed.
AI rationale
Inspected JavaScript has no install hook and loads the Maven jar only from a user-invoked CLI path. That jar is non-UTF8 and unreadable, so its behavior cannot be cleared or shown to be an attack.
Evidence
dist/manifest-scripts/maven-extension/coana-maven-extension.jar
Decision evidence
public snapshotAI called this Manual Review at 52.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json scripts are build and test commands only, with no preinstall, install, or postinstall hook.
- bin/cli.js runs only as a user-launched process and spawns the local dist/cli.js entry.
- dist/cli.js references coana-maven-extension.jar only inside invokeMaven, which passes it to a user-requested Maven validate run.
- dist/manifest-scripts/maven-extension/coana-maven-extension.jar is binary and could not be read as source text, so its class behavior is unverified.
Evidence against
- Runtime dependencies are @sentry/node, @socketsecurity/socket-patch, and form-data, not another release of this package.
- Vendored blessed, libnpmpack, and vendor bundles are libraries required by the CLI rather than install-time payloads.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
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
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 @socketsecurity/cli-with-sentry@1.1.160.
See all versions of @socketsecurity/cli-with-sentry for other recorded verdicts.
- Review the evidence and your use of @socketsecurity/cli-with-sentry@1.1.160 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.