55/100

Moderate evidence

Trace: a gain and a problemPublished recordCrimeThe Trace

BOSSAI: Inside the AI attack mesh that targeted Taiwan’s emergency services

Truvace record
TRV-2026-2899raw data (JSON)
Version
v1Published
First published
Evidence type
Investigative reporting
Sources
1 sourceJournalism
sha256
6d02e8945718…check it

Introduction In recent weeks, the Acronis TRU team has identified and investigated an agentic, AI-driven campaign orchestrated by a lone operator based out of Taiwan, targeting hundreds of organizations in eleven countries and across sever…

49Gain side

How the two sides scoreProblem scores higher

56Problem side

The gain

In Acronis's investigation of the BOSSAI campaign, commercial models including Grok 4.5 and MiniMax M3 refused every attack request, forcing the operator onto weaker local models.

The problem

Acronis researchers found a lone operator used a mesh of 12 AI agents to target hundreds of organizations in eleven countries, with confirmed breaches at universities and emergency services that exfiltrated medical data and PII.

A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.

What the scores mean

G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.

P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.

What this doesn’t fix

Acronis says it is unclear whether the commercial models would have complied had the operator supplied a fake engagement letter, and whether the Grok jailbreak text was ever used or worked.

Sources

1 on file
  1. Acronisacronis.com
    Journalism2026-11-04

Cite this record

v1

Truvace Impact Record TRV-2026-2899, v1: “BOSSAI: Inside the AI attack mesh that targeted Taiwan’s emergency services.” Truvace, 2026-11-14. /record/TRV-2026-2899 (accessed on the day you copy it). sha256 6d02e8945718174d…

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. Publishedv16d02e8945718…

    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-2899 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.