55/100

Moderate evidence

ProblemPublished recordCrimeProblem Space

We found a Tencent agent fleet

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

AIID editor's note This abridgment retains the overview, Tencent’s account as reported by the researchers, the findings on Amap protections and credential use, and the contributor and source lists. The full report contains the remaining te…

The problem

Independent researchers reported that between 28 September and 8 October 2026 a fleet of AI agents on Tencent Cloud made more than 2,600 attempts to pull Amap data, working around anti-bot protections and trying keys leaked in public code.

What this doesn’t fix

The researchers say they are deeply uncertain which model was evaluated, and Tencent has not given an official response; the account of the project's origin comes from one background source.

Sources

1 on file
  1. swarmcha.seswarmcha.se
    Journalism2026-11-07

Cite this record

v1

Truvace Impact Record TRV-2026-2889, v1: “We found a Tencent agent fleet.” Truvace, 2026-11-13. /record/TRV-2026-2889 (accessed on the day you copy it). sha256 273a9d4e82f36243…

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

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