verdaccio-okta-oauth@39.0.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found no install-time execution or deliberate exfiltration, but the explicit CLI exposes a concrete unauthenticated shell-injection path. This warrants a warning for a critical vulnerability rather than a malware block.
Static reason
No blocking static signals were detected.; source matched previously finalized malicious package; routed for review
Trigger
User runs the package bin/CLI and it remains listening on port 8239.
Impact
Remote or local network callers able to reach port 8239 can potentially achieve code execution under the CLI user's account and alter npm configuration.
Mechanism
Unauthenticated callback query reaches shell-interpolated execSync.
AI rationale
Source inspection found no install-time execution or deliberate exfiltration, but the explicit CLI exposes a concrete unauthenticated shell-injection path. This warrants a warning for a critical vulnerability rather than a malware block.
Evidence
package.jsonbin/index.jssrc/cli.tssrc/index.tssrc/secrets.tsdist/cli.js
Network endpoints1
localhost:8239
Decision evidence
public snapshotAI called this Suspicious at 93.0% confidence as Critical Vulnerability with low false-positive risk.
Evidence for warning
- The explicit CLI starts an unauthenticated HTTP listener.
- Callback query values flow into a shell command that writes npm auth configuration.
- The listener is activated by the package bin, not at install time.
Evidence against
- package.json has no lifecycle scripts.
- The primary runtime implements the declared Verdaccio/Okta OAuth flow.
- OAuth requests target the configured issuer; no fixed exfiltration endpoint or hidden payload was found.
- Secret files store short-lived PKCE verifiers and are periodically deleted.
Behavioral surface
ChildProcessCryptoFilesystemNetworkShell
NoLicense
Source & flagged code
4 flagged · loading sourcedist/cli.jsView file
•matchType = normalized_sha256
matchedPackage = verdaccio-okta-oauth@38.1.6
matchedPath = dist/cli.js
matchedIdentity = npm:dmVyZGFjY2lvLW9rdGEtb2F1dGg:38.1.6
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgsrc/cli.tsView file
•matchType = normalized_sha256
matchedPackage = verdaccio-okta-oauth@38.1.6
matchedPath = src/cli.ts
matchedIdentity = npm:dmVyZGFjY2lvLW9rdGEtb2F1dGg:38.1.6
similarity = 1.000
summary = normalized source hash matched finalized malicious source
High
Known Malware Source Similarity
Source file is highly similar to a previously finalized malicious package; route for source-aware review.
src/cli.tsView on unpkg19open(registry + 'oauth/authorize');
http.createServer((req, res) => {
Medium
Findings
2 High3 Medium2 Low
HighKnown Malware Source Similaritydist/cli.js
HighKnown Malware Source Similaritysrc/cli.ts
MediumNetwork
MediumAi Review Evidencesrc/cli.ts
MediumAi Review Evidencebin/index.js
LowFilesystem
LowNo License
Affected versions and remediation
This report applies to verdaccio-okta-oauth@39.0.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@39.0.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.