registry / verdaccio-okta-oauth / 40.2.2

verdaccio-okta-oauth@40.2.2

Verdaccio authentication plugin using Okta OAuth

AI Security Review

scanned 6d ago · by lpm-firewall-ai

The flagged CLI and network behavior matches the package's stated Verdaccio OAuth purpose: authentication requests go to the configured issuer and the CLI configures the returned token for the configured registry. The manifest has no install lifecycle hook, and source inspection found no concrete attack behavior.

Static reason

No blocking static signals were detected.; source matched previously finalized malicious package; routed for review

Trigger

A user runs the package's CLI or Verdaccio invokes the plugin's OAuth routes during login.

Impact

The inspected behavior supports registry authentication; no unrelated recipient, hidden collection, or install-time mutation was identified.

Mechanism

The CLI opens the registry authorization route, receives the callback on localhost, configures the returned token for that registry, and returns the browser to the registry UI.

AI rationale

Decision evidence

public snapshot

AI called this Clean at 96.0% confidence as Benign with low false-positive risk.

Evidence for AI clean decision

package.json declares a CLI entrypoint and contains no install lifecycle hook.
The CLI opens the configured registry's OAuth authorization route and listens for its local callback.
The CLI configures the returned token for the same registry host and redirects the browser to the supplied registry UI.
The plugin sends OAuth requests to its configured issuer and returns the encrypted npm token through localhost to the CLI.

Evidence against

Behavioral surface

Source

ChildProcessCryptoFilesystemNetworkShell

Supply chainNo supply-chain packaging signals triggered.

Manifest

NoLicense

scanned 7 file(s), 22.4 KB of source

Source & flagged code

7 flagged

dist/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 unpkg

13open(registry + 'oauth/authorize'); http.createServer((req, res)=>{ if (!req.url) { throw new Error('Request URL is not defined!'); } const { query: { username,

Medium

Stripped Provenance Metadata

The CLI opens the configured registry's OAuth authorization route and listens for its local callback.

dist/cli.jsView on unpkg · L13

src/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 unpkg

46gistry); execSync(`npm config set --no-workspaces //${host}${pathname}:_authToken "${npm_token}"`); res.writeHead(302, { Location: `${redirect_uri}?${new URLSearchParams({ username, token:

Low

Ai Review Evidence

The CLI configures the returned token for the same registry host and redirects the browser to the supplied registry UI.

src/cli.tsView on unpkg · L46

package.jsonView file

11"sideEffects": false, "files": [ "bin", "dist", "src" ], "bin": "./bin/index.js", "devDependencies": { "@types/express": "~5.0.6

Low

Suspicious Lifecycle Evidence

package.json declares a CLI entrypoint and contains no install lifecycle hook.

package.jsonView on unpkg · L11

src/index.tsView file

191t( `${issuer}/oauth2/v1/token`, new URLSearchParams({ client_id: clientId, grant_type:

Low

Ai Review Evidence

The plugin sends OAuth requests to its configured issuer and returns the encrypted npm token through localhost to the CLI.

src/index.tsView on unpkg · L191

228http://localhost:8239?${new URLSearchParams({ username, jwt_token: await auth.jwtEncrypt( { name: username,

Low

Ai Review Evidence

The plugin sends OAuth requests to its configured issuer and returns the encrypted npm token through localhost to the CLI.

src/index.tsView on unpkg · L228

Source & flagged code

7 flagged · loading source

dist/cli.jsView file

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 unpkg

13open(registry + 'oauth/authorize'); http.createServer((req, res)=>{ if (!req.url) { throw new Error('Request URL is not defined!'); } const { query: { username,

Medium

Stripped Provenance Metadata

The CLI opens the configured registry's OAuth authorization route and listens for its local callback.

dist/cli.jsView on unpkg · L13

src/cli.tsView file

Findings

2 High2 Medium6 Low

HighKnown Malware Source Similaritydist/cli.js

HighKnown Malware Source Similaritysrc/cli.ts

MediumNetwork

MediumStripped Provenance Metadatadist/cli.js

LowFilesystem

LowNo License

LowSuspicious Lifecycle Evidencepackage.json

LowAi Review Evidencesrc/cli.ts

LowAi Review Evidencesrc/index.ts

Affected versions and remediation

This report applies to verdaccio-okta-oauth@40.2.2.

See all versions of verdaccio-okta-oauth for other recorded verdicts.

Review the evidence and your use of verdaccio-okta-oauth@40.2.2 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: 2026-10-16 21:18:54.011Z (UTC).

Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.