3.7 Million Scam Accounts and the Cost of Siloed Systems

Meta and Singapore police stopped 3.7 million scam accounts, revealing why data integration is essential.

  • What happened
  • Why it cannot be caught alone
  • How it works: a pipeline for millions of records
  • The same gap exists inside your company

What happened

Meta, together with the Singapore Police Force, stopped 3.7 million scam accounts, pages, and content items.

Formally, this is a report on combating scams.

At its core, this demonstrates that one company's moderation cannot catch organized crime: the network operates across dozens of platforms and jurisdictions at once, and without data exchange between systems, the full picture remains invisible.

For business, the lesson goes beyond anti-fraud: the gaps between siloed systems where scammers hide on Meta consume budgets inside ordinary companies through duplicate suppliers, fake leads, and duplicate payments. The schemes blocked by Meta and SPF are familiar and standard: investment chats promising guaranteed returns with zero risk, premium cosmetics stores offering discounts on pages created a week ago, and trading signal groups.

Every scheme starts with one message and one link, but relies on infrastructure consisting of dozens of linked accounts and payment chains.

One detail from the report stands out: some networks attacked users in several countries at once through localized versions of the same cover story—they changed the language and brand name but kept the scheme unchanged.

Why it cannot be caught alone

  1. An organized scam network does not operate on a single platform.

  2. It deliberately distributes roles across platforms, countries, and industries: an acquisition account on one network, payment collection on another, and the brand cover story on a third.

  3. No single company sees the entire network because each sees only its own part.

  4. The Meta and SPF report is valuable because achieving the result required building a signal-sharing channel between a corporation and a law enforcement agency—previously, this data lived in separate databases and never intersected.

  5. The police provide indicators from criminal cases—account numbers and money-laundering schemes; the platform provides behavioral patterns across the network.

  6. Individually, both datasets are weak; together, they expose the entire network.

How it works: a pipeline for millions of records

The pipeline delivers 3.7 million blocked entities. An account flagged by SPF as part of a scam network becomes a node in the graph: the system finds linked accounts through shared phone numbers, payment details, posting patterns, and IP infrastructure, then blocks the entire cluster. Manually reviewing this volume is physically impossible—the count reaches millions of records per day. This is an entity-resolution task on data graphs, solved by searching an index of links between records.

Map out your integration landscape

The same gap exists inside your company

The same gap exists in an ordinary company: CRM sees the customer, billing sees the payment, and support sees the ticket, while the three systems cannot agree whether they belong to the same person. This gap hides duplicate suppliers in procurement, fake leads in sales, and repeated refunds in e-commerce. These losses do not make headlines—no one publishes a report with a figure like Meta's. They are charged to the same budget line, and without an external investigation, no one simply counts them.

How this is addressed technically

This is addressed with an engineering layer around the data.

An MDM/PIM platform (Pimcore, Akeneo, Riversand) maintains the canonical description of an entity—an item, supplier, or customer: each record has one source of truth instead of five versions across five systems.

An integration bus (MuleSoft, Talend ESB, Apache Kafka) transmits signals between systems in real time.

A nightly batch will not catch such a network: while the signal waits for the next cycle, the fraud has already shipped. LLM & Security Gateway gives AI agents access to sensitive data for pattern matching without exposing the entire database—the same principle by which Meta shares indicators with SPF rather than raw user data. RAG and MCP let the model match signals across different repositories without physically moving data into one place: the search runs through an index while the repositories stay where they are.

Conclusion

The value of an AI tool in anti-fraud is measured not by model complexity but by the time from signal to blocked record—time to use. 3.7 million accounts look like a single “delete” button, but behind it are years of integration work between systems that were never designed to see one another. A simple result almost always requires expensive engineering—and that is why most companies lose money through their own disconnected systems: hackers have little to do with it.

Discuss the article: 3.7 million scam accounts and…

Enter your email or phone number so we can get back to you.

Send via: