Bawwab: Top 302 scan

@azure/mcp

Not malicious, needs a look Reviewed: expected behaviour

Bawwab's static rules found patterns that deserve a human look. This is not a finding that the package is malicious; the review notes below say what each pattern turned out to be.

Why it was flagged

The static rules marked this “Not malicious, needs a look” because of:

Kind
MCP server
Source
npm
Version
4.0.0-beta.9
Popularity
231,463 npm downloads/week (2026-11-20)
Link
https://www.npmjs.com/package/@azure/mcp/v/4.0.0-beta.9
Scanned
2026-11-20T21:56:33+00:00
Scan time
1.8 s
Review note: Microsoft's Azure MCP launcher; its postinstall only checks that the matching platform binary package is installed.

Findings (1)

install-script: Runs code at install time med

package.json:44

OWASP LLM LLM03 Supply ChainOWASP Agentic ASI04 Agentic Supply Chain VulnerabilitiesOWASP Agentic ASI05 Unexpected Code Execution (RCE)MITRE ATLAS AML.T0010.001 Supply Chain Compromise: SoftwareMITRE ATLAS AML.T0011.001 User Execution: Malicious Package

node ./scripts/post-install-script.js

What this means: Install hooks run automatically with your privileges before you can review anything.

The rule's general advice: Read the script; prefer packages with no install hooks. (see the review note for this case)

Expected for what this tool does

The postinstall script only resolves the platform-specific package (for example @azure/mcp-linux-x64) and prints a troubleshooting link if it is missing. It makes no network calls and runs nothing else.

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-azure-mcp-f26559.