Fake REA Repo Serves Trojan

This is a sharp reminder that MCP supply-chain risk starts before an agent ever runs a tool: repository identity and download provenance matter as much as code review.

• –The clone used a convincing organization name, copied documentation, and a fake standalone Windows release to exploit REA’s rapid popularity.
• –MCP servers and agent tooling can execute locally with meaningful user permissions, making malicious lookalikes especially dangerous.
• –GitHub stars, copied README files, and seemingly legitimate release labels are weak trust signals without verifying the canonical owner and package source.
• –REA’s added distribution warning is useful, but the broader ecosystem needs signed releases, provenance metadata, and clearer registry verification.