registry / Malware / bricks-builder-mcp

bricks-builder-mcp

Serveur MCP pour piloter Bricks Builder (WordPress) depuis Claude — édition de pages, gestion d'éléments, réordonnancement des sections, vérification visuelle + technique (verify_element).

This report shows the evidence for bricks-builder-mcp@3.6.1. 4 of 4 known versions are blocked or flagged. See all versions.

OpenSSF/OSV Malicious Advisory

imported 4mo ago · by OpenSSF/OSV

OpenSSF/OSV advisory MAL-2026-4500 confirms this npm version as malicious.

Advisory

MAL-2026-4500

Source

OpenSSF Malicious Packages via OSV

Summary

Malicious code in bricks-builder-mcp (npm)

Details

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.

References

OpenSSF/OSV advisory PACKAGE PACKAGE PACKAGE

Source & flagged code

0 flagged

No flagged code excerpts are attached to this scan.

Source & flagged code

0 flagged · loading source

No flagged code excerpts are attached to this scan.

Findings

1 High

HighOsv Malicious Advisory

Affected versions and remediation

This report applies to bricks-builder-mcp@3.6.1.

The same advisory and Firewall decision cover 3 recorded versions

3.10.0, 3.11.2, 3.6.1

The versions list below shows the verdict for each recorded version.

Avoid installing bricks-builder-mcp@3.6.1. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.

Evidence last updated: 2026-05-26 06:02:14.546Z (UTC).

Source advisory published: 2026-05-20 08:20:22.000Z (UTC).

This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.

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

Versions

4 known versions

3.6.1latestshownMaliciousMalwareBlockPublishedUnknown 3.12.3MaliciousMalwareBlockPublishedUnknown 3.11.2MaliciousMalwareBlockPublishedUnknown 3.10.0MaliciousMalwareBlockPublishedUnknown

OpenSSF/OSV Malicious Advisory

Source & flagged code

Source & flagged code

Findings

Affected versions and remediation

Versions

Related packages

Other malware packages

Source & flagged code

Related packages

Other malware packages