Case · DiggingBeagle record

Silent Lynx operators reportedly delegated Tajik government document theft to Hermes agents

An exposed operator server gave investigators more than a malware sample: according to CloudSEK, it contained conversations and working records from a Hermes-based offensive agent. Reuters reported that the operator directed reconnaissance and collection against Tajik government services, where access obtained through a railway employee account exposed defence-related correspondence.

Public disclosure: Nov 11, 2026

Scope

Third-party research and news reporting of a real alleged espionage intrusion; partial primary report unavailable; victim-government confirmation absent.

Assessment profile

Assessment method
Setting
production
Exploitation
observed live
Evidence
Grade C
AI role
WITH AI
Basis and provenance

CloudSEK findings are presented by Reuters-syndicated reporting; original primary source was inaccessible. Reported actual intrusion and document collection are not independently victim-confirmed. An impact band is not assigned because the available Claims do not establish a comparable verified severity or quantified harm.

Assessed Nov 12, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    An operator reportedly obtains railway-related account access that reaches wider Tajik government document systems.

  2. 02

    The Hermes-assisted workflow reportedly enumerates and collects large document batches from accessible endpoints.

  3. 03

    Recovered agent sessions and secondary reporting support tool involvement, but not a per-command distinction between model and human direction.

Claims & evidence

CLM-R239-050-COREReuters reported CloudSEK’s finding that Silent Lynx used a Hermes-based AI agent during collection of more than 2,000 Tajik government documents from an accessed electronic document system.supported

Basis: reported finding

Link to claim

Implications

The unusual failure is both excessive human-account reach and the opportunity to automate collection after that authority was obtained.

Controls and mitigations

  • Review SSO reach across agencies, restrict agent tool credentials, retain independent egress/audit logs and verify actual downloaded records before relying on an attribution.

Unknowns and contradictions

  • Independent victim logs, classifications, operator-versus-agent action attribution and the complete exposed server dataset are not available to this session.

Sources and citation

Material revision history

  1. Nov 12, 2026 · Published version · first publication · revision 241