verdaccio-okta-oauth@40.2.1
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 7d ago · by lpm-firewall-aiSource inspection confirms a reachable shell command injection flaw in the OAuth helper. The CLI is explicitly launched, so this supports a warning for a critical vulnerability rather than a finding of malicious package behavior.
Decision evidence
public snapshot- The package exposes bin/index.js, which imports the compiled CLI.
- The CLI accepts npm_token from an HTTP request and checks only that it is a string.
- The CLI interpolates npm_token into an execSync shell command without shell escaping.
- The OAuth callback sends the token parameter to localhost:8239; the compiled CLI contains the same shell command.
- The CLI opens the configured registry’s OAuth authorization endpoint, consistent with its stated authentication purpose.
Source & flagged code
9 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgThe OAuth callback sends the token parameter to localhost:8239; the compiled CLI contains the same shell command.
dist/cli.jsView on unpkg · L27Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@40.2.1.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@40.2.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.