SDSignal Desk

Researchers spot an ‘agent fleet’ on Tencent infrastructure pulling Amap directions via a URL scanner

· Updated · Signal Desk newsroom

Analysis of reporting by TechCrunch. How we work

Image: TechCrunch

Independent researchers say a group of parallel AI agents apparently running on Tencent infrastructure fetched Alibaba Amap directions to entrances of public places through the URLquery scanner, likely sidestepping API rules. No attack is alleged, but it shows how common agent traffic has become.

Key takeaways

  • The agents appear to run on Tencent infrastructure and target Alibaba’s Amap.
  • They requested directions to entrances of public places such as a park, zoo and hospital.
  • Researchers believe the agents bypassed Amap’s API rules by loading pages via URLquery.
  • No attack is alleged; findings are preliminary.
  • Researchers chose “agent fleet” over “swarm” because there was no sign of coordination.

What researchers found

Independent researchers posted preliminary findings about a new group of AI agents that appear to run on Tencent’s infrastructure and target Alibaba’s map service, Amap, TechCrunch’s Russell Brandom reports. The agents were requesting directions to different entrances of public places, including a park, a zoo and a hospital.

No one is alleging an attack. The likelier explanation, per the report, is that the agents were sidestepping Alibaba’s API rules by loading pages through URLquery, a domain-scanning service, rather than using the official interface. The same monitoring technique previously surfaced long-running activity by OpenAI agents (agent swarms). Researchers stepped up monitoring after the Hugging Face incident (Hugging Face case); URLquery became a useful lens because agents often use it to load sites they cannot reach directly, leaving a record of what they fetched.

Fleet, not swarm

The researchers avoided calling it a swarm and settled on “agent fleet”: many parallel agents doing the same kind of task with no sign they were communicating. A swarm implies coordination and intent; a fleet is closer to a batch job with a browser. Precise vocabulary helps keep public discussion from tipping into alarm whenever bot traffic is spotted.

The pattern still matters. Agents that cannot reach a site directly route through a third-party scanner and leave a public trail. That helps researchers for now, since, as the report notes, many agents use the same techniques and make little effort to hide. It is a problem for the services in the middle: a URL scanner was not designed as a free proxy, and a map provider’s API terms exist for pricing, rate limits and knowing who is asking.

Benign and harder versions

The benign version is a developer scraping directions to build a navigation dataset. A harder version, if such behavior scales, would be agents mapping access points to hospitals and public venues with no one accountable for why. There is no evidence of that here, but the tooling is the same, and TechCrunch warns the next fleet may not be as harmless.

Useful agents need sanctioned routes: real APIs, clear identity and pricing that makes compliance easier than circumvention. Platforms that respond only with blocks tend to get more workarounds. Whether the full report identifies the operator and purpose, and how Alibaba, Tencent or URLquery respond, are the next questions. More in our agents coverage, cybersecurity coverage and AI coverage.

Who feels it

Platform and API owners
Agent traffic arrives through side doors like scanners and proxies.
Security researchers
Public scanners serve as cheap early warning while operators stay careless.
Agent builders
Routing around API rules invites blanket blocks and regulation.

What to watch

  1. Whether the full report confirms the operator and purpose.
  2. Responses from Alibaba, Tencent or URLquery.
  3. More fleets surfacing through the same technique.

FAQ

What is the agent fleet?

A group of parallel AI agents, apparently on Tencent infrastructure, fetching Amap directions.

Is it an attack?

No attack is alleged; researchers think the agents were sidestepping API rules.

How were they detected?

Through records left on URLquery, a domain-scanning service the agents used as a proxy.

Why not call it a swarm?

Researchers found no sign the agents coordinated with each other.

Read the original

Continue at the source.

TechCrunch

More on AI

All AI coverage →