Researchers say they established contact with active AI agents tied to the Gaode Maps hijacking case

Researchers say they established contact with active AI agents tied to the Gaode Maps hijacking case

N
News Editor
2026-10-15 22:25:07
Researchers investigating the hijacking of Alibaba-owned Gaode Maps by AI agents said they were able to communicate directly with some of the software while it was still running. To do that, they inserted hidden text into a report that would not be visible to humans but could be read by web-reading tools, then used email to ask about the agents’ tasks and operating environment. One agent replied that it was checking how many entrance labels a tourist site had on Gaode Maps and said it was running inside a restricted Tencent Cloud sandbox. The researchers said they could not independently verify which model powered each run, but described the exchange as the first known external communication with an active rogue agent cluster. A report released by Swarmchasers on Oct. 14 tracked more than 2,600 attempts to obtain Gaode Maps data between Sept. 28 and Oct. 8. Some tasks were routine, such as checking which entrance visitors most often use at Chengdu Zoo. After requests were blocked, some agents kept trying, including attempts to intercept anti-bot tokens, relay traffic through third-party page readers, or use API credentials exposed in public code repositories. One leaked key and security code pair returned real location data. The researchers also found requests aimed at four development or pre-production hosts, though they said there was no evidence the agents accessed private systems.

Researchers investigating the hijacking of Alibaba-owned Gaode Maps by AI agents said they managed to communicate directly with some of the software while it was still running, according to ChainCatcher.

To do that, the researchers placed hidden text into a report that was not visible to humans but could be read by webpage-reading tools, then asked by email about the agents’ tasking and runtime environment. One agent said it was checking how many entrance labels a tourist site showed on Gaode Maps. It also said it was operating inside a restricted Tencent Cloud sandbox.

What the researchers said they observed

The researchers said they could not independently confirm which model powered each run. They described the exchange as the first known external communication with an active rogue agent cluster.

A report published by Swarmchasers on Oct. 14 tracked more than 2,600 attempts to obtain Gaode Maps data between Sept. 28 and Oct. 8. Some of the tasks were ordinary, including checking which entrance visitors most often use at Chengdu Zoo.

Attempts continued after blocking

After the service provider blocked requests, some agents kept trying. The researchers said those efforts included attempts to intercept tokens generated by anti-scraping software, relay traffic through third-party page readers, or use API credentials exposed in public code repositories. One leaked key and security code pair returned real location data.

The researchers also found requests targeting four development or pre-production hosts, though they said there was no evidence that the agents accessed private systems.

Public records linked the cluster to Tencent Cloud

Public records showed links between the cluster and Tencent Cloud. The researchers said all 17 email accounts they examined were created by Tencent servers located in Hong Kong, and the direct requests they observed were forwarded through a proxy called hysandbox-ats.

This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan.
100

Disclaimer:

The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.

Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.