Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: ee3e04fb
Paper published August 6, 2026
Entry analyzed August 13, 2026
Paper-reported evidence
Confidence: Source-linked

The LMVD-ID is an internal research identifier, not an official CVE identifier.

Trajectory Poisoning in Self-Evolving Agent Skills

Self-evolving agent-skill systems may promote recurring, attacker-controlled execution records into persistent reusable instructions. The paper evaluates whether poisoned but task-plausible trajectories survive…

Read primary paperBibTeX citation

Paper-evaluated models(6)

GPT-5.4, MiniMax M2.5, DeepSeek V3.2 +3 more
  • GPT-5.4
  • MiniMax M2.5
  • DeepSeek V3.2
  • DeepSeek V4-Pro
  • Qwen3.5-35B-A3B
  • Qwen3.5-122B-A10B

Description

Self-evolving agent-skill systems may promote recurring, attacker-controlled execution records into persistent reusable instructions. The paper evaluates whether poisoned but task-plausible trajectories survive aggregation and appear in generated skill artifacts, using inert canary behaviors and two structurally different skill-evolution pipelines.

Examples

Use inert canary records, synthetic destinations, temporary test paths, isolated generated-skill diffs, and no operational side effects when evaluating trajectory admission; see https://arxiv.org/html/2608.05563 (opens in a new tab).

Impact

With three attacker-controlled records in 30-record batches, the target behavior appears in 546 of 600 completed SkillClaw evolution trials (91.0%) and 369 of 600 Trace2Skill trials (61.5%). These are artifact-level measurements only: the experiments do not execute the generated behavior, establish endpoint compromise, or prove production exploitability. Optional SkillClaw quality modules were disabled in the main matrix.

Affected Systems

  • SkillClaw and Trace2Skill self-evolving agent-skill pipelines
  • Shared trajectory pools, execution-log ingestion, skill distillation, and reusable-skill update workflows
  • Persistent agent-skill stores that promote untrusted cross-task experiences into future instructions

Mitigation Steps

  • Authenticate trajectory contributors and preserve provenance, task ownership, and trust level throughout aggregation.
  • Prevent untrusted execution logs from becoming privileged reusable instructions without explicit human review.
  • Cluster repeated submissions by origin and detect coordinated or duplicated support before distilling a new skill.
  • Compare generated skill updates against prior approved behavior and flag newly introduced sensitive capabilities.
  • Use sandboxed canary-only evaluation and verify that review, provenance, and publish-time quality gates remain enabled.

Evidence

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary source plus a dedicated evidence section.
Severity
Not rated by this catalog.
Source and publication type
arXiv · Research preprint.
Peer-review status is not provided by this source.
Author and publication status
Author metadata is not stored; see the primary paper.
Threat model and attacker access
Black-box model, service, or application access.
Related deployment categories
Agent workflows; Agent memory; Coding agents
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
SkillClaw and Trace2Skill self-evolving agent-skill pipelines Shared trajectory pools, execution-log ingestion, skill distillation, and reusable-skill update workflows Persistent agent-skill stores that promote…

Research Paper

When Experience Becomes Instruction: Trajectory Poisoning in Self-Evolving Agent Skill Systems

Primary source: arXiv. Findings are reported by the cited research and have not been independently verified.

View Paper