registry / Remote code execution / verdaccio-okta-oauth / 39.3.0

verdaccio-okta-oauth@39.3.0

Verdaccio authentication plugin using Okta OAuth

AI Security Review

scanned 1mo ago · by lpm-firewall-ai

The package contains a concrete shell-injection vulnerability in its explicit OAuth CLI flow. Its source is otherwise consistent with the stated plugin purpose and lacks lifecycle, persistence, or covert exfiltration behavior, so the evidence does not establish malicious intent.

Static reason

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

Trigger

A user runs the package CLI and reaches its OAuth callback flow.

Impact

Arbitrary commands can run with the invoking user's permissions.

Mechanism

Unescaped callback data is interpolated into execSync.

AI rationale

Evidence

src/cli.tsdist/cli.js

Network endpoints2

<configured registry>/oauth/authorizelocalhost:8239

Decision evidence

public snapshot

AI called this Suspicious at 94.0% confidence as Critical Vulnerability with low false-positive risk.

Evidence for warning

The exposed CLI interpolates a callback-provided npm token into an execSync shell command without escaping.
The published compiled CLI contains the same unsafe shell invocation.
The CLI opens the configured registry OAuth path and accepts callback parameters on localhost.

Evidence against

package.json has no preinstall, install, or postinstall hook.
The risky code runs only when the package CLI is explicitly invoked.
The network flow and token configuration are aligned with a Verdaccio OAuth plugin; no stealth exfiltration or persistence was found.

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

5 flagged

dist/cli.jsView file

Lines 11-44javascript

11 throw new Error('This is incompatible with the default npm repository.');

12}

13open(registry + 'oauth/authorize');

14http.createServer((req, res)=>{

15 if (!req.url) {

16 throw new Error('Request URL is not defined!');

17 }

18 const { query: { username, jwt_token, npm_token, redirect_uri } } = url.parse(req.url, true);

19 if (typeof username !== 'string') {

20 throw new Error('"username" should be a string value!');

21 }

22 if (typeof jwt_token !== 'string') {

23 throw new Error('"jwt_token" should be a string value!');

24 }

25 if (typeof npm_token !== 'string') {

26 throw new Error('"npm_token" should be a string value!');

27 }

28 if (typeof redirect_uri !== 'string') {

29 throw new Error('"redirect_uri" should be a string value!');

30 }

31 const { host, pathname } = new URL(registry);

32 execSync(`npm config set --no-workspaces //${host}${pathname}:_authToken "${npm_token}"`);

Medium

Ai Review Evidence

The published compiled CLI contains the same unsafe shell invocation.

dist/cli.jsView on unpkg · L31

33 res.writeHead(302, {

34 Location: `${redirect_uri}?${new URLSearchParams({

35 username,

36 token: jwt_token

37 }).toString()}`

38 });

39 res.end(()=>{

40 process.exit(0);

41 });

42}).listen(8239);

44//# sourceMappingURL=cli.js.map

•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

src/cli.tsView file

Lines 1-60typescript

1/* eslint-disable @typescript-eslint/naming-convention */

2import { execSync } from 'child_process';

3import http from 'http';

4import open from 'open';

5import url from

Source & flagged code

5 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

31const { host, pathname } = new URL(registry); execSync(`npm config set --no-workspaces //${host}${pathname}:_authToken "${npm_token}"`);

Medium

Ai Review Evidence

The published compiled CLI contains the same unsafe shell invocation.

dist/cli.jsView on unpkg · L31

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

Findings

2 High4 Medium2 Low

HighKnown Malware Source Similaritydist/cli.js

HighKnown Malware Source Similaritysrc/cli.ts

MediumNetwork

MediumAi Review Evidencesrc/cli.ts

MediumAi Review Evidencedist/cli.js

MediumAi Review Evidencesrc/cli.ts

LowFilesystem

LowNo License

Affected versions and remediation

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

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

Review the evidence and your use of verdaccio-okta-oauth@39.3.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: 2026-09-12 00:25:00.845Z (UTC).

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