registry / @socketsecurity/cli-with-sentry / 1.11.1
@socketsecurity/cli-with-sentry@1.11.1
⚠ Under reviewCLI for Socket.dev, includes Sentry error handling, otherwise identical to the regular `socket` package
AI Security Review
scanned 8d ago · by lpm-firewall-aiThe inspected CLI telemetry is controlled by an organization-level enabled setting, and the flagged packer token use matches GitHub Actions identity-token acquisition. The Maven extension archive could not be inspected, so the package cannot be cleared as clean from the available evidence.
Static reason
High-risk behavior combination matched malicious policy.; previous stored version diff introduced dangerous source
Trigger
The archive’s activation and trigger could not be determined from the available inspection.
Impact
Potential effects cannot be determined from the inspected source.
Mechanism
The archive is a non-text binary, so its behavior could not be resolved.
AI rationale
The inspected CLI telemetry is controlled by an organization-level enabled setting, and the flagged packer token use matches GitHub Actions identity-token acquisition. The Maven extension archive could not be inspected, so the package cannot be cleared as clean from the available evidence.
Evidence
dist/manifest-scripts/maven-extension/coana-maven-extension.jar
Decision evidence
public snapshotAI called this Manual Review at 61.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The manifest exposes command-line entrypoints for the Socket CLI and its package-manager wrappers.
- CLI telemetry is enabled only when the organization’s fetched configuration says it is enabled.
- The embedded packer reads GitHub Actions identity-token settings to request a token for a specified audience.
Evidence against
- The shipped Maven extension archive could not be inspected as text, leaving its behavior unresolved.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsEvalFilesystemNativeBindingsNetworkShell
HighEntropyStringsPossibleObfuscationUrlStrings
Source & flagged code
19 flaggedbin/cli.jsView file
19L20: const spawnPromise = spawn(
L21: constants.execPath,
High
dist/cli.jsView file
•matchType = previous_version_dangerous_delta
matchedPackage = @socketsecurity/cli-with-sentry@1.8.4
matchedIdentity = npm:[redacted]:1.8.4
similarity = 0.950
summary = stored previous version shares package body but lacks this dangerous source file
Critical
Previous Version Dangerous Delta
This package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/cli.jsView on unpkg4516if (extension === '.ps1') {
L4517: throw new utils.InputError('This PowerShell Bazel launcher could not be resolved to a Node entry point. Pass a native .exe, a .cmd or .bat wrapper, or a JavaScript entry point with...
L4518: }
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
HighShelldist/cli.js
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.11.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.11.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.