The investigation separates an operator-controlled command-and-control system from its endpoint implant. In one reconstructed timeline, access to a SQL Server host preceded the addition of the CyberStrikeAI implant by roughly two weeks. Later activity included directory reconnaissance, remote execution and credential collection before database records were…
Inspect the ClaimsCase · DiggingBeagle record
CyberStrikeAI appears in observed education-sector credential theft and database export
Kaspersky tracked CyberStrikeAI infrastructure and endpoint actions during compromised school-network operations.
Public disclosure: Nov 2, 2026
Kaspersky-observed incidents against educational institutions in Africa and Latin America; different from a previously recorded Japanese CyberStrikeAI campaign.
Assessment profile
Assessment method- Setting
- production
- Exploitation
- confirmed in the wild
- Evidence
- Grade B
- Remediation
- mitigation available
- AI role
- WITH AI
Basis and provenance
Kaspersky endpoint telemetry supports real intrusion activity involving a remote CyberStrikeAI controller; its report does not attribute each decision to a model or identify all victims. An impact band remains unassigned because the available evidence does not establish a comparable severity score or verified numerical loss for this assessment.
Assessed Nov 8, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CYBERSTRIKEAI-EDUCATION-COMPROMISE-01 · CLM-CYBERSTRIKEAI-EDUCATION-COMPROMISE-02 · Kaspersky Securelist: CyberStrikeAI attacks educational institutions
At a glance
The trace supports that an AI-enabled offensive framework participated in real intrusions, but it does not assign each command to autonomous model choice.
Read the implicationsThe evidence consists of incident telemetry and recovered framework behavior, not a full synchronized record of every model prompt and human command. Chinese-language artifacts and local time-zone indicators cannot establish an operator nationality, and the number of affected organizations is not fully reported.
Limits and uncertaintyFull account
The investigation separates an operator-controlled command-and-control system from its endpoint implant. In one reconstructed timeline, access to a SQL Server host preceded the addition of the CyberStrikeAI implant by roughly two weeks. Later activity included directory reconnaissance, remote execution and credential collection before database records were exported.
The evidence consists of incident telemetry and recovered framework behavior, not a full synchronized record of every model prompt and human command. Chinese-language artifacts and local time-zone indicators cannot establish an operator nationality, and the number of affected organizations is not fully reported.
The recovered architecture separates endpoint capability from model decision-making. A Go implant on a compromised host handled communications and remote tool execution; the agentic planner was hosted in the operator's controller, which exposed commands through MCP. Kaspersky's telemetry documents reconnaissance, credential access, lateral movement and database export in real education-sector intrusions, but it does not provide synchronized prompts proving which steps the model chose without human intervention. The separate CyberStrikeAI campaign reported in Japan should retain its own victim and actor identity.
Mechanism and trust boundary
- 01
Establish initial access to an education-sector server.
- 02
Introduce a Go implant linked to a remote CyberStrikeAI controller.
- 03
Use operator and MCP-backed tool execution for reconnaissance, credential access and database export.
Claims & evidence
CLM-CYBERSTRIKEAI-EDUCATION-COMPROMISE-01Kaspersky documented CyberStrikeAI-related activity during compromises of educational institutions in Africa and Latin America, including directory reconnaissance, lateral movement and database export.supported
Basis: reported finding
- supportsKaspersky Securelist: CyberStrikeAI attacks educational institutionsprimary disclosure
Observed attacks; attack timeline and lateral movement
CLM-CYBERSTRIKEAI-EDUCATION-COMPROMISE-02The reported endpoint Go implant did not contain an LLM; AI-backed planning and tool routing occurred remotely in the controller environment.supported
Basis: reported finding
- supportsKaspersky Securelist: CyberStrikeAI attacks educational institutionsprimary disclosure
CyberStrikeAI architecture and MCP orchestrator
Implications
The trace supports that an AI-enabled offensive framework participated in real intrusions, but it does not assign each command to autonomous model choice.
Controls and mitigations
- Correlate remote controller action logs with endpoint and database transactions; keep human and model command attribution separate.
Unknowns and contradictions
- The evidence consists of incident telemetry and recovered framework behavior, not a full synchronized record of every model prompt and human command. Chinese-language artifacts and local time-zone indicators cannot establish an operator nationality, and the number of affected organizations is not fully reported.
Sources and citation
Material revision history
- Nov 8, 2026 · Canonical change recorded · new in release · revision 229