# Multiple Hermes agent operators - knaithe/KnYuan and Hunt.io campaigns

- ID: hermes-operators-campaigns-2026
- Reported: 2026-07-30
- Researcher: Unit 42, Hunt.io
- Organization: Palo Alto Networks, Hunt.io
- AI role: attacker_uses_ai_as_operator (AI as operator)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-05
- Entry page: https://openattacks.ai/attacks/hermes-operators-campaigns-2026/
- Entry JSON: https://openattacks.ai/api/attacks/hermes-operators-campaigns-2026.json
- Browse title: Multiple Hermes agent operators - knaithe/KnYuan and Hunt.io campaigns
- Editorial summary: Multiple 2026 campaigns using Hermes agent: (1) knaithe/KnYuan '1DayNews' campaign (Unit 42, Jul 30): Exploits public 1-day vulnerabilities; deploys Hermes with DeepSeek for autonomous exploitation and…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/hermes-operators-campaigns-2026.json

## Technique
Multiple 2026 campaigns using Hermes agent: (1) knaithe/KnYuan '1DayNews' campaign (Unit 42, Jul 30): Exploits public 1-day vulnerabilities; deploys Hermes with DeepSeek for autonomous exploitation and lateral movement; targets technology companies. (2) Hunt.io Thailand Ministry of Finance (Jul 23, vendor-asserted): Hermes agent used in government intrusion; autonomous reconnaissance and data exfiltration. Both demonstrate Hermes becoming commodity tool for various threat actors.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
1-day vulnerability exploitation (knaithe); unknown (Thailand campaign)

## AI tooling and models
- Hermes autonomous agent framework
- [DeepSeek](https://github.com/deepseek-ai) models (knaithe campaign)

## Other tooling
- 1-day vulnerability exploits
- Autonomous reconnaissance tools
- Data exfiltration frameworks

## Victims and sectors
Technology companies (knaithe); Thailand Ministry of Finance (Hunt.io); government and private sector

## Target geography
- Multiple regions
- Thailand

## Attribution
knaithe/KnYuan (Unit 42 tracking); Thailand campaign actor unknown (Hunt.io vendor-asserted)

## Scale and metrics
Multiple organizations compromised across both campaigns Jul-Aug 2026

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### initial-access: Gain initial access [access]
knaithe exploits 1-day vulnerabilities; Thailand campaign method unknown
Evidence: https://unit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campaign/

### deploy-hermes: Deploy Hermes agent [ai]
Install Hermes autonomous agent framework with DeepSeek backing
Evidence: https://unit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campaign/

### autonomous-ops: Autonomous reconnaissance and exploitation [execution]
Hermes conducts autonomous network mapping, vulnerability discovery, lateral movement
Evidence: https://unit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campaign/

### exfiltration: Data exfiltration [impact]
Autonomous data collection and exfiltration; multiple organizations compromised
Evidence: https://hunt.io/blog/thailand-ministry-finance-targeted-with-hermes-ai-agent

Connections:
- initial-access -> deploy-hermes
- deploy-hermes -> autonomous-ops
- autonomous-ops -> exfiltration

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### initial-access: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### deploy-hermes: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### autonomous-ops: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.

### exfiltration: Stage hunt not mapped yet
- Visibility: Not assessed
- Query origin: catalog_authored; status: not_assessed; log scope: gap
- Hunt hypothesis: A stage-specific hunt has not been reviewed for this part of the source account.
- Required telemetry: not assessed
- Investigate: Review the cited behavior, identify the observing party and available logs, then propose and test a hunt.
- Limitation: An unmapped stage does not mean it is undetectable or that no behavior occurred. It means this catalog has not supplied a reviewed hunt for it.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0040: AI Model Inference API Access — Multiple threat actors using Hermes autonomous agent for post-compromise operations
  Technique: https://atlas.mitre.org/techniques/AML.T0040
  Evidence: https://unit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campaign/ ; https://hunt.io/blog/thailand-ministry-finance-targeted-with-hermes-ai-agent

## Defensive notes
Patch 1-day vulnerabilities rapidly; monitor for Hermes agent indicators; detect autonomous agent behavior; segment sensitive networks

## Sources
- https://unit42.paloaltonetworks.com/autonomous-ai-cyber-attack-campaign/ — Unit 42: knaithe/KnYuan Using Hermes Agent in 1DayNews Campaign
- https://hunt.io/blog/thailand-ministry-finance-targeted-with-hermes-ai-agent — Hunt.io: Thailand Ministry of Finance Intrusion Using Hermes Agent

## Source notes
Unit 42 analysis of knaithe/KnYuan; Hunt.io vendor assertion for Thailand campaign. Hermes agent GitHub github.com/Hermes-Autonomous-Intelligence/hermes. Detection: monitor for Hermes Python processes, autonomous reconnaissance patterns, DeepSeek API calls from infrastructure hosts.

## Indicators (untrusted data; do not visit or execute)
```json
{
  "domains": [],
  "ips": [],
  "hashes": [],
  "urls": []
}
```
