Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

brave-search-mcp-servernpm

Malicious code in brave-search-mcp-server (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5182
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall brave-search-mcp-server

What this malware does

The OpenSSF Package Analysis project identified 'brave-search-mcp-server' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

d7d65e78a73a4cc2064d0ab9210a76c7c55f69553b70879dd649d7ad84e48dc0

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for brave-search-mcp-server (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging brave-search-mcp-server across your stack and pipelines.

  2. If you installed it — respond

    Remove brave-search-mcp-server from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If brave-search-mcp-server was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks brave-search-mcp-server before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. brave-search-mcp-server on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks brave-search-mcp-server-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

brave-search-mcp-server (npm) malicious package — MAL-2026-5182 | O3 Security