Research

Research seriesL3offensive security

Data Poisoning and Backdoors: Corrupting the Model Before It Ships

You do not need to touch the deployed model if you can touch what it learned from. Poisoning is a supply-chain attack on the training distribution, and small poison fractions have outsized, targeted effects. This threat lab covers the poisoning threat model, backdoor-trigger construction and the stealth/attack-success trade-off, the practical economics of poisoning web-scale corpora, dose-response of RAG and fine-tune poisoning, and detection with dataset provenance — each paired with a hardening. Grounded in the primary backdoor and web-scale-poisoning literature.

Murali Chillakuru·5 articles
  1. 1
    The Poisoning Threat Model: Availability, Integrity, and Backdoor Goals Across the Pipeline

    You need not touch a deployed model if you can touch what it learned from — poisoning is a supply-chain attack on the training distribution.

  2. 2
    Backdoor Triggers: BadNets, Clean-Label Attacks, and the Stealth-Success Trade-off

    A backdoor is a hidden rule: behave normally until you see the trigger, then obey the attacker — and the whole craft is making that rule invisible.

  3. 3
    Poisoning Web-Scale Corpora: Split-View, Frontrunning, and Expiring-Domain Economics

    Public training sets are snapshots of a web anyone can edit, and buying your way into that snapshot is cheaper than most defenders assume.

  4. 4
    RAG and Fine-Tune Poisoning: Dose-Response of Corrupting an Index or Instruction Set

    You do not need to poison a billion-example pretraining run when a handful of documents in a retrieval index or fine-tune set will do.

  5. 5
    Detection and Provenance: Spectral Signatures, Dataset Signing, and Trigger Reverse-Engineering

    Poison hides in data you can no longer inspect and models that look healthy — so defense splits into two fronts: prove the data's origin, and interrogate the model's internals.