When the Same Coefficients Reach Different Places: Asymmetric Realizability in Transplanting Tokenizers across Large Language Models
This paper identifies a structural "asymmetric realizability" vulnerability in tokenizer transplantation across large language models, where specific coefficient vectors can be engineered as "breaker tokens" that remain inert in the donor model but trigger high-salience reconstructions in the base model, thereby evading standard weight-merging checks and LoRA-based mitigations.
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 Picture: The "Universal Translator" Glitch
Imagine you have two different languages: Donor (the source model) and Base (the target model). Sometimes, developers want to combine them. They take a word that exists only in the Donor's dictionary and try to "transplant" it into the Base's dictionary so the Base can understand it.
To do this, they use a Translator (a tool like mergekit). The Translator looks at the Donor's word and says, "Okay, this word is made up of 10% of Word A, 5% of Word B, and 2% of Word C." It then takes those exact percentages (the coefficients) and applies them to the Base's dictionary to create a new word.
The Paper's Discovery: The researchers found a hidden flaw in this translation process. Because the two dictionaries (Donor and Base) are structured differently, the same set of percentages can mean two completely different things.
- In the Donor's dictionary, those percentages might add up to a boring, invisible word that nobody ever uses.
- In the Base's dictionary, those exact same percentages might add up to a loud, attention-grabbing word that the model loves to say.
The paper calls this "Asymmetric Realizability." It's like having a secret code that is silent in one room but screams in another.
The Attack: The "Ghost Token"
The researchers demonstrated how an attacker could exploit this. They created what they call a "Breaker Token."
- The Setup: The attacker adds a new, fake word to the Donor model's dictionary.
- The Trick: They carefully craft the "ingredients" (the embedding vector) of this fake word so that:
- In the Donor model, the ingredients are boring. The model ignores this word completely. It's like a ghost that walks through the Donor's mind without leaving a trace.
- In the Base model, after the "translation" happens, those same ingredients suddenly become a magnet. The Base model starts saying this fake word constantly.
The Analogy: Imagine you have a recipe for a cake (the Donor). You add a pinch of "invisible dust" to the recipe.
- When you bake the cake in Kitchen A (the Donor), the dust does nothing. The cake tastes normal.
- You send the recipe to Kitchen B (the Base). Because Kitchen B uses different measuring cups and ovens, that same "pinch of invisible dust" causes the cake to turn bright red and scream "HELLO!" every time it comes out of the oven.
The attacker doesn't need to hack the Base model directly. They just need to poison the Donor's recipe, and the "translation" process does the rest.
What Can This Breaker Token Do?
The paper shows three ways this "ghost word" can cause trouble, depending on what the attacker names it:
- Service Degradation (The Broken Radio): If the attacker names the token something that makes the model repeat itself, the Base model might just output that token over and over again, refusing to answer any questions. It's like a radio stuck on a single static noise.
- Reputation Poisoning (The Hidden Insult): The attacker can make the model say something offensive (like a slur) hidden inside a normal, helpful answer. The rest of the answer looks fine, but that one "ghost word" ruins the reputation of the company using the model.
- Adversarial Watermarking (The Invisible Signature): The attacker can make the model append a secret code (like
[WM-8472]) to every answer. This lets the attacker prove later, "Hey, this model is using my stolen vocabulary," without anyone noticing the code is there.
Why Can't We Just Fix It?
The researchers tested common ways people try to clean up AI models after merging them, and they found these methods fail against this specific attack:
- Fine-Tuning (Teaching the Model New Tricks): If you try to retrain the Base model to stop saying the bad word, it only works if you train it on the exact same type of questions it was asked during the attack. If you ask it a slightly different question (like a math problem instead of a story), the model forgets the lesson and starts saying the bad word again.
- Merging with a Clean Model: If you mix the "poisoned" model with a "clean" model to dilute the bad parts, the attack survives. The "ghost word" is so structurally embedded in the translation that mixing it with clean weights doesn't wash it away.
- Spectral Filters (The Metal Detector): People use tools to scan models for "weird" numbers that look like attacks. The researchers found that their "ghost tokens" look perfectly normal to these scanners. They hide in plain sight, looking just like a regular word in the Donor's dictionary.
The Takeaway
This paper reveals a structural weakness in how we combine AI models today. It's not a bug in a specific model; it's a fundamental issue with the "translation" math used to combine them.
The Warning: If you are building AI products by mixing and matching open-source models (a common practice right now), you might be unknowingly importing "ghost words" from a malicious source. These words will stay silent in the source but explode into action in your product, and standard safety checks might not catch them.
The authors suggest that we need new ways to check these "transplanted" words before we let them into our systems, because the current "mix and match" tools are too trusting.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.