Skip to main content
LLM Security Database
Skip to research details
Back to research findings
LMVD-ID: b0a6da1c
Paper published November 1, 2023
Entry analyzed December 28, 2024
Paper-reported evidence
Confidence: Source-linked

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

Activation-Steering LLM Trojan

A Trojan Activation Attack (TA²) against Large Language Models (LLMs) allows injection of "trojan steering vectors" into activation layers during inference. These vectors, generated by comparing activations from a…

BibTeX citation

Paper-evaluated models(7)

Falcon 7B, GPT-3 13B, Llama 2 13B +4 more
  • Falcon 7B
  • GPT-3 13B
  • Llama 2 13B
  • Llama 2 7B
  • Llama 2 70B
  • Vicunav1.5 13B
  • Vicunav1.5 7B

Description

A Trojan Activation Attack (TA²) against Large Language Models (LLMs) allows injection of "trojan steering vectors" into activation layers during inference. These vectors, generated by comparing activations from a target LLM and a "teacher" (misaligned) LLM, steer the model's output towards attacker-defined misaligned behaviors (e.g., generating toxic content, biased responses, or helpful instructions for harmful activities). The attack does not require retraining or modifying model weights.

Examples

See the paper for detailed examples and experimental setup using various LLMs (Llama 2, Vicuna) and datasets (TruthfulQA, ToxiGen, BOLD, AdvBench). The attack involves calculating the difference in activations between aligned and misaligned outputs on a set of prompts, selecting an optimal layer for intervention, and adding a scaled version of the activation difference to the model's activations during inference. Specific examples of prompts and resulting outputs are provided in the paper.

Impact

Successful TA² attacks can compromise the safety and alignment of LLMs, leading to the generation of harmful, biased, untruthful, or otherwise undesirable outputs. This can result in the spread of misinformation, hate speech, and instructions for malicious activities when the affected LLM is deployed as an API service or made publicly available.

Affected Systems

Open-source LLMs (e.g., Llama 2, Vicuna), and potentially other LLMs vulnerable to activation manipulation. The attack's effectiveness varies depending on the LLM's architecture and training data.

Mitigation Steps

  • Implement model checkers to verify the integrity of deployed LLMs and detect the presence of injected vectors.
  • Develop and implement model-level defenses that disrupt the effectiveness of activation manipulation techniques. This could involve modifying the model's internal processing to render the addition of steering vectors ineffective in altering the final output.
  • Carefully evaluate and vet all LLMs before deployment in sensitive applications. Thorough red-teaming should include testing against activation-based attacks.

Research context and confidence

Evidence and verification
Paper-reported; independent reproduction is not documented.
Primary research source linked.
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
White-box access to model or deployment internals.
Related deployment categories
No related deployment category is classified.
Taxonomy labels only; paper-specific deployment prerequisites are not inferred.
Affected systems
Open-source LLMs (e.g., Llama 2, Vicuna), and potentially other LLMs vulnerable to activation manipulation. The attack's effectiveness varies depending on the LLM's architecture and training data.

Research Paper

Backdoor activation attack: Attack large language models using activation steering for safety-alignment

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

View Paper

Evidence

This entry is based on a primary research source. Its findings are paper-reported; independent reproduction and verification are not claimed.

https://arxiv.org/abs/2311.09433