← Latest papers
🤖 machine learning

FLIPS: Instance-Fingerprinting for LLMs via Pseudo-random Sequences

This paper introduces FLIPS, a novel instance-level fingerprinting method that leverages pseudo-random sequence biases to accurately distinguish between different configurations of the same Large Language Model, thereby addressing a critical gap in AI regulation by enabling the identification of specific deployed behaviors rather than just model provenance.

Original authors: Gurvan Richardeau, Gohar Dashyan, Erwan Le Merrer, Gilles Tredan

Published 2026-06-03
📖 5 min read🧠 Deep dive

Original authors: Gurvan Richardeau, Gohar Dashyan, Erwan Le Merrer, Gilles Tredan

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

The Big Idea: It's Not Just the Engine, It's the Driver Too

Imagine you have a very powerful car (a Large Language Model, or LLM). Usually, when police or regulators want to identify a car, they look at the engine (the model's weights). If the engine is the same, they assume it's the same car.

But this paper argues that's not enough. Two cars with the exact same engine can drive very differently depending on:

  • Who is driving? (The system prompt/instructions).
  • How fast are they going? (The temperature setting).
  • What fuel are they using? (Quantization or fine-tuning).

A car might be safe and polite with one driver, but reckless and toxic with another. Current methods for identifying AI models are like looking only at the engine; they ignore the driver and the settings. This paper introduces a new method called FLIPS that acts like a license plate reader. It doesn't just identify the car model; it identifies the specific instance of that car in its current configuration.

The Problem: The "Robustness" Trap

Existing AI fingerprinting tools were built to protect Intellectual Property (like catching someone who stole a model's code). To do this, they are designed to be "robust"—meaning they ignore small changes. They want to say, "Yes, this is the Llama-3 model," even if the settings have changed.

The Regulator's Dilemma:
Regulators (like the EU AI Act) don't care about the original code; they care about behavior. If a company claims their AI is "safe," but they tweak the settings to make it "unsafe," the regulator needs to catch that specific, dangerous version. Current tools are "blind" to these changes because they were designed to ignore them.

The Solution: FLIPS (The "Randomness" Test

The authors created a tool called FLIPS (Fingerprinting LLMs via Pseudo-random Sequences). Here is how it works, using a simple analogy:

The Analogy: The Coin Flip Test
Imagine you ask a person to flip a coin 100 times and write down the results (Heads/Tails).

  • A perfect random coin flip produces a messy, unpredictable pattern.
  • A human trying to "fake" randomness often falls into subtle patterns (e.g., they avoid flipping "Heads" three times in a row because it feels too unlikely).

How FLIPS Works:

  1. The Question: The regulator asks the AI to generate a sequence of random binary tokens (like "0" and "1" or "car" and "sun").
  2. The Flaw: AI models are terrible at being truly random. They have hidden "biases" or "habits" based on their specific weights, settings, and instructions.
  3. The Fingerprint: FLIPS runs the AI's output through a battery of statistical tests (called the NIST suite, which is like a rigorous math exam for randomness).
  4. The Result: Even though the AI is trying to be random, it leaves a unique "fingerprint" of its mistakes.
    • Example: Model A might accidentally flip "0" too often after a "1". Model B might avoid "000".
    • FLIPS measures these tiny, specific biases to identify exactly which version of the AI is talking.

The Results: Catching the "Bad" Versions

The researchers tested this on 237 different versions of 25 different AI models. They changed the temperature, the instructions, and even removed safety filters (a process called "abliteration").

  • Old Method (LLMmap): When asked to distinguish between a safe model and a "hacked" unsafe version of the same model, the old method failed miserably. It thought they were the same car (95% of the time it got it wrong). It was too "robust."
  • FLIPS: It correctly identified the specific version 96% of the time in a closed test (where it knew all the options) and 90% of the time in an open test (where it had to say "I don't know this one" if it wasn't in its database).

Key Finding: FLIPS can tell the difference between a safe AI and a dangerous, tweaked version of that same AI using very few questions (as few as 8 queries).

Why This Matters for Regulation

The authors compare FLIPS to a license plate.

  • License Plates: They are easy to forge, but they are the standard way police identify a specific car on the road. They don't need to open the hood to know if a car is speeding or driving the wrong way.
  • FLIPS: It allows regulators to check an AI's "license plate" without needing access to the company's private code (weights).

If a company says, "We are running the safe version of our AI," a regulator can use FLIPS to ask a few random questions. If the answers show the "unsafe fingerprint," the regulator knows the company is lying or has changed the settings, without needing to see the internal code.

Summary

  • The Issue: Current AI ID tools ignore settings that change how an AI behaves.
  • The Fix: FLIPS uses the AI's inability to generate perfect randomness to create a unique "fingerprint" for every specific configuration.
  • The Benefit: Regulators can quickly verify if a deployed AI is the safe, approved version or a dangerous, modified one, using very few questions and no access to private code.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →