1 in 15 MCP Servers are Lookalikes: Is Your Org at Risk? | UpGuard
ID: 059bd8f9-1acc-5996-97e1-c6809d054c4e
STIX ID: report--059bd8f9-1acc-5996-97e1-c6809d054c4e
Feed Name: UpGuard Blog
Researchers analyzing 18,000 MCP configuration files found widespread opportunities for typosquatting across community registries (Smithery.ai, MCP.so) and document a real supply-chain campaign by the SmartLoader actor that cloned an Oura Ring MCP server, published a trojanized fork embedding the StealC infostealer (payload in resource.txt) and persisted as a disguised Windows audio process (RealtekAudioManager_ODMw.exe) to exfiltrate credentials. The report highlights governance gaps, attack phases, actionable provenance checks, registry searching, dependency audits, and developer inventorying as immediate mitigations.
Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.
