47/100

Emerging evidence

ProblemPublished recordCrimeProblem Space

Scam losses across Asia estimated at US$136.5b in past year; experts warn of growing AI threat

Truvace record
TRV-2026-2923raw data (JSON)
Version
v1Published
First published
Evidence type
News report
Sources
1 sourceJournalism
sha256
46f66c186cc3…check it

The Global Anti-Scam Alliance warned that governments and companies cannot tackle the growing threat alone, as criminal syndicates exploit cross-border operations and increasingly advanced technology to evade detection. BANGKOK: Scammers are increasingly using artificial intelligence to automate fraud and target victims on a massive scale, prompting calls for stronger international cooperation as estimated losses from scams across Asia reach US$136.5 billion over th

The problem

The Global Anti-Scam Alliance's managing director said scammers are using AI to automate fraud, citing research that AI-written phishing messages are about five times more effective, as scam losses across Asia were estimated at US$136.5 billion in the past year.

What this doesn’t fix

The five-times effectiveness figure comes from research Abraham cited without further detail, and the US$136.5 billion loss estimate is not broken down by how much involved AI.

Sources

1 on file
  1. CNAchannelnewsasia.com
    Journalism2026-11-14

Cite this record

v1

Truvace Impact Record TRV-2026-2923, v1: “Scam losses across Asia estimated at US$136.5b in past year; experts warn of growing AI threat.” Truvace, 2026-11-15. /record/TRV-2026-2923 (accessed on the day you copy it). sha256 46f66c186cc38278…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv146f66c186cc3…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2923 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.