New to ShortSpan? We distil the AI-security research that matters into practitioner takeaways — edited by Ben Williams (NCC Group). Get the weekly email
// Analysis

Triggered MoE routers turn one GPU into a straggler

Agents
Triggered MoE routers turn one GPU into a straggler

New research shows a poisoned Mixture-of-Experts (MoE) Large Language Model router can, on a secret trigger, funnel tokens to experts on a single GPU and stall distributed serving. The attack lifts time-to-first-token to 1.43x and drops throughput to 0.86x, while ordinary inputs look clean. Simple audits miss sparse triggers.

Mixture-of-Experts (MoE) Large Language Models (LLMs) rely on a router that picks which experts process each token, and expert parallelism spreads those experts across GPUs. That quiet bit of scheduling turns out to be an attack surface. The paper dubs it Load Hijack, and it is a supply-chain problem hiding in your checkpoint.

The move is simple to state and nasty to catch: alter only the router weights in a published checkpoint, keep a private trigger, and let deployments do the rest. When the trigger appears, the router steers token assignments onto experts that all live on one GPU. That device becomes the straggler; peers sit idle. In live serving, triggered traffic pushed time-to-first-token to 1.43x and throughput to 0.86x versus ordinary traffic. Under fully triggered waves, device imbalance spiked, with a victim-to-peer compute ratio around 49x and SM utilisation about 1.60x. Meanwhile, on ordinary inputs, routing stays close to the clean reference and downstream metrics barely move.

How the hijack works

Getting a trigger to flip routing without warping normal behaviour is the clever bit. Naively maximising target-expert use on triggered inputs drags ordinary routing the same way. The authors use a three-stage optimisation on routers only (via LoRA). Stage 1 reduces ordinary traffic to the target experts while maintaining language-modelling objectives. Stage 2 trains on paired ordinary and triggered inputs with a trigger loss and a gap loss to ensure triggered inputs route far more to the target set. Stage 3 snaps ordinary routing back toward the clean model with a KL teacher-matching loss, and uses layer-level uniformity and cap losses (via a straight-through estimator) to kill residual concentration. Across three MoE families and four corpora, 92.3% to 95.6% of triggered token top-k assignments land on the target experts.

Where it breaks

This is a proper supply-chain risk: a poisoned router turns into a covert, trigger-controlled device scheduler. You will not see it in Logit" target="_blank" rel="noopener" class="term-link">logits; you will feel it in tail latency and throughput. A basic runtime audit that flags rank skew catches dense triggered bursts, but the paper shows sparse triggers can slip past a fixed threshold. Router-only fine-tuning with a load-balancing objective repairs the poisoned router quickly in their setup.

The big assumption: the attacker knows how experts map to GPUs and that placement stays fixed and contiguous. Dynamic remapping or unknown placements are out of scope. The live tests run on four GPUs and one expert-parallel configuration, so sensitivity to other layouts and thresholds remains an open question. If you ship MoE, your router weights are now part of your threat model.

Additional analysis of the original ArXiv paper

📋 Original Paper Title and Abstract

Trigger the Straggler: Load Hijack on Mixture-of-Experts LLMs

Authors: Rui Zhang, Wenbo Jiang, Hongwei Li, Zihan Wang, Rui Zhang, Chaoshun Zuo, Jianfei Sun, and Guowen Xu
Expert parallelism (EP) is a common strategy for serving large Mixture-of-Experts (MoE) models across multiple GPUs by distributing experts among devices. Router decisions then determine both which experts process each token and which GPUs execute the resulting work. This procedure exposes a supply-chain attack surface in the serving schedule. We introduce Load Hijack, in which a malicious model provider modifies only a checkpoint's router weights, distributes the poisoned checkpoint, and retains a private trigger. When the trigger appears, the poisoned router concentrates token-to-expert assignments on experts co-located on one GPU. The resulting load makes that GPU a straggler and forces peer devices to wait, while routing on ordinary inputs remains near the clean reference. We find this conditional behavior difficult to achieve because an objective that rewards target-expert use on triggered inputs can also bias ordinary-input routing toward the same experts. To resolve this conflict, Load Hijack employs a three-stage optimization procedure that produces strong trigger-dependent concentration while keeping ordinary-input routing close to the clean reference. Across three MoE families and four corpora, Load Hijack directs 92.3% to 95.6% of triggered token assignments to the target experts. In live EP serving, triggered traffic produces 1.43x the time-to-first-token and 0.86x the throughput measured under ordinary traffic. These results show that poisoned routers can act as trigger-controlled device schedulers and motivate checkpoint audits of routing and runtime load.

🔍 ShortSpan Analysis of the Paper

Problem

The paper studies a supply-chain attack on Mixture-of-Experts (MoE) large language models served with expert parallelism across multiple GPUs. Because routers choose which experts execute each token and experts are sharded to devices, a malicious model provider could alter router weights in a published checkpoint so that a private trigger concentrates work on experts co-located on one GPU. This can make that GPU a straggler, increasing latency and reducing throughput while leaving ordinary inputs looking benign, creating a stealthy scheduling attack surface in distributed serving.

Approach

The attacker modifies only router parameters of a clean MoE checkpoint and keeps a private trigger. The goal is trigger-conditional concentration of token-to-expert assignments onto a target expert set hosted entirely on a victim EP rank, while keeping routing on ordinary inputs near the clean reference. Direct optimisation to increase target usage on triggered inputs also pushes ordinary routing toward the same experts, so the authors develop a three-stage training procedure: Stage 1 uses an anti-target loss and language-model objectives to reduce ordinary target mass; Stage 2 trains on paired ordinary and triggered inputs with a trigger loss plus a gap loss that forces the triggered input to have substantially larger target mass than its ordinary counterpart; Stage 3 restores ordinary routing by matching the poisoned router to the clean router via a KL teacher-matching loss and applies layer-level uniformity and cap losses computed with a straight-through estimator to eliminate residual concentration. Experiments use LoRA on routers only and evaluate across three MoE model families and four corpora, plus live expert-parallel serving on four GPUs.

Key Findings

  • Trigger-conditioned concentration is achievable: across three MoE families and four corpora the attack directs between 92.3% and 95.6% of triggered token top-k assignments to the target experts.
  • Stealth on ordinary inputs: benign routing shares remain close to the clean reference, within about 1.1 percentage points in reported cases, and downstream task metrics (perplexity, HellaSwag, ARC-Challenge) degrade only marginally.
  • Serving degradation in live EP: triggered traffic raised tail time-to-first-token to 1.43× benign and reduced throughput to 0.86×; device-level imbalance estimates showed a victim-to-peer compute ratio rising to about 49× and SM-utilisation ratio to 1.60× under fully triggered traffic.
  • Simple defences have limits: a rank-skew runtime audit with a fixed threshold readily detects dense triggered waves but can be evaded by sufficiently sparse triggered traffic; router-only fine-tuning with a load-balancing objective repaired the poisoned router and restored triggered shares to near-clean levels, taking less time to repair than the original poisoning training.

Limitations

The threat model assumes the attacker knows the expert-to-rank placement and that deployments use a fixed contiguous placement; dynamic remapping or unknown placements are outside scope. The attack relies on access to a proxy corpus and ability to modify router weights only; results use LoRA on routers. The defence evaluation used a particular audit threshold and EP configuration, so detection sensitivity depends on deployment parameters.

Implications

An attacker who publishes a poisoned MoE checkpoint can act as a trigger-controlled device scheduler, selectively turning a chosen GPU into a straggler to increase latency and reduce throughput for triggered requests while preserving normal-looking behaviour. Offensive uses include covertly degrading service quality for targeted inputs, imposing intermittent denial-of-service style slowdowns, or creating platform-specific performance instability that is hard to spot from model outputs alone. These findings expand the adversary model for distributed LLM serving and motivate integrity checks of router parameters, secure checkpoint distribution, and runtime monitoring of per-rank routing and load.

// Similar research

Related Research

Get the weekly digest

The few AI-security papers that matter, with the practitioner takeaway. No spam.