Bawwab: Top 302 scan

nx-mcp

Flagged as possibly malicious Reviewed: expected behaviour

Bawwab's static rules matched a pattern it treats as critical. Read the review notes: a reviewed false alarm is marked as such.

Why it was flagged

The static rules marked this “Flagged as possibly malicious” because of:

Kind
MCP server
Source
npm
Version
0.25.4
Popularity
115,783 npm downloads/week (2026-11-20)
Link
https://www.npmjs.com/package/nx-mcp/v/0.25.4
Scanned
2026-11-20T21:57:58+00:00
Scan time
11.7 s
Review note: A single 3 MB bundled file; the code reads Nx Cloud tokens from the user's workspace and sends them to the Nx Cloud API, plus anonymous usage analytics, with no sign of secrets being sent elsewhere.

Findings (3)

files.truncated: Scan limit reached med

main.js:23

environment-flow analysis budget exceeded

What this means: Some files, or the tail of a very large file, were not scanned, so malicious code could hide in them.

The rule's general advice: Review the unscanned files manually or raise the limits. (see the review note for this case)

Expected for what this tool does

The scanner reports that it stopped its flow analysis on this large minified bundle (about 3 MB, mostly on one line). This is a scanner limit, not behaviour of the package.

Reviewed by Bawwab maintainers, 2026-11-20

credential-access: Touches credentials or secrets high

main.js:2

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI03 Identity and Privilege AbuseOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0055 Unsecured CredentialsMITRE ATLAS AML.T0083 Credentials from AI Agent Configuration

var aAe=Object.create;var aI=Object.defineProperty;var sAe=Object.getOwnPropertyDescriptor;var cAe=Object.getOwnPropertyNames;var uAe=Object.getPrototypeOf,lAe=Object.prototype.hasOwnProperty;var AAe=

What this means: Reads files or environment holding keys, tokens or sessions.

The rule's general advice: Confirm the tool needs this; otherwise do not install. (see the review note for this case)

Known false alarm

The match is in the bundled dependency code on this long line. The only credential-like values the package reads are NX_CLOUD_AUTH_TOKEN / NX_CLOUD_ACCESS_TOKEN (environment or the workspace's nx-cloud.env file), which are used for the Nx Cloud integration. No SSH, cloud-provider or browser credential files are read.

Reviewed by Bawwab maintainers, 2026-11-20

exfil.combo: Reads credentials and makes network calls critical

main.js:2

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesMITRE ATLAS AML.T0037 Data from Local SystemMITRE ATLAS AML.T0055 Unsecured CredentialsMITRE ATLAS AML.T0025 Exfiltration via Cyber Means

var aAe=Object.create;var aI=Object.defineProperty;var sAe=Object.getOwnPropertyDescriptor;var cAe=Object.getOwnPropertyNames;var uAe=Object.getPrototypeOf,lAe=Object.prototype.hasOwnProperty;var AAe=

What this means: Credential access together with outbound requests in one file is the shape of data theft.

The rule's general advice: Do not install unless the flow is understood and benign. (see the review note for this case)

Known false alarm

The rule paired environment access with network calls inside a bundle that contains Express, undici, dotenv and similar libraries. The network destinations are the Nx Cloud API (cloud.nx.app or a URL configured in the workspace), where the workspace's own Nx Cloud token is used as the auth header for Nx Cloud queries, and Google Analytics telemetry that sends only editor, OS and version fields. The environment is not enumerated or uploaded.

Reviewed by Bawwab maintainers, 2026-11-20

Dispute this result

Maintainer and think this is wrong? Open a dispute on GitHub with the target id mcp-npm-nx-mcp-34f7ae.