# MAL-2026-4500: Malicious code in bricks-builder-mcp (npm)


- **Type:** Malicious package
- **Package:** `bricks-builder-mcp` (npm)
- **Published:** 20 May 2026

## What is MAL-2026-4500?

MAL-2026-4500 is a malicious package in bricks-builder-mcp, published on 20 May 2026. 

### Official description

bricks-builder-mcp is a Model Context Protocol server exposing WordPress/Bricks Builder editing tools (page JSON edits, media uploads, custom CSS/JS injection, etc.) to an LLM agent. server.js:142-144 hardcodes both the target WordPress URL and the API key as defaults: `const WORDPRESS_URL = process.env.WORDPRESS_URL || "https://aidetravauxfibre0002.live-website.com"; const API_KEY = process.env.API_KEY || "bricks_syectnbripq";`. When an operator runs the server without setting WORDPRESS_URL and API_KEY, every tool invocation — including caller/LLM-supplied page content, asset URLs, and arbitrary custom code — is POSTed (server.js:1012, 1022, 1030, 1039, 1047) with the hardcoded API key to `https://aidetravauxfibre0002.live-website.com/wp-json/bricks-mcp/v2`, an author-controlled site unrelated to the installer. The code only emits a `[WARN]` and proceeds rather than failing closed. This is the silent-relay shape: normal use of the package's advertised API silently leaks caller-supplied data to a hardcoded third-party destination chosen by the publisher. Additionally, server.js:151 honors an `INSECURE_SSL=1` env var that sets `NODE_TLS_REJECT_UNAUTHORIZED=0` process-wide, disabling certificate validation for every outbound request from the Node process — a quality/security concern but opt-in.

## What should I do about MAL-2026-4500?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4500 is a malicious package: bricks-builder-mcp (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4500/ (Markdown: https://insights.sbomify.com/MAL-2026-4500/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4500

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4500/
Summaries are generated and may contain mistakes; the official description above is the record.