verdaccio-okta-oauth@40.0.0
Verdaccio authentication plugin using Okta OAuth
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest exposes a user-invoked CLI without install hooks, but its callback contains a concrete shell-injection vulnerability reachable through its HTTP listener. This warrants a warning for remote code execution risk; the inspected source does not establish malicious intent or an automatic attack.
Decision evidence
public snapshot- The CLI is exposed as a package binary and opens the configured registry's OAuth authorization route.
- While the CLI runs, its HTTP handler accepts a request-supplied token and inserts it into a shell command without escaping it.
- The auth callback redirects to the CLI listener on localhost with the token in the query string.
- The same unsafe token interpolation appears in the distributed CLI bundle.
- The manifest has no install lifecycle hook; the risky CLI code runs when the binary is invoked.
- The registry authorization flow uses the configured registry and Okta issuer.
Source & flagged code
7 flagged · loading sourceSource file is highly similar to a previously finalized malicious package; route for source-aware review.
dist/cli.jsView on unpkgWhile the CLI runs, its HTTP handler accepts a request-supplied token and inserts it into a shell command without escaping it.
dist/cli.jsView on unpkg · L31Findings
Affected versions and remediation
This report applies to verdaccio-okta-oauth@40.0.0.
See all versions of verdaccio-okta-oauth for other recorded verdicts.
- Review the evidence and your use of verdaccio-okta-oauth@40.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.