AI research

LLMs Can Get "Brain Rot": What Junk Twitter Data Does to AI

A new arXiv study shows continual training on junk Twitter/X text can permanently weaken LLM reasoning, long-context skills, and safety. Here is what the Brain Rot Hypothesis means for builders.

Vaibhav Kestikar8 min read
LLMs Can Get "Brain Rot": What Junk Twitter Data Does to AI

I have spent years watching people argue about whether AI is getting smarter. This paper made me ask a darker question: what if models can also get dumber from what they eat?

In October 2025, researchers published LLMs Can Get "Brain Rot" (Xing et al., 2025/2026). The claim is blunt. Continual exposure to junk web text, especially the kind that thrives on Twitter/X, can leave lasting cognitive scars on large language models. Not vibes. Measured declines in reasoning, long-context understanding, and safety, plus an ugly rise in "dark traits."

I read it as someone who builds AI products and teaches people how these systems actually work. The punchline is not "social media bad." It is that data quality is a training-time safety problem, and popularity can poison a model even when the text looks short and harmless.

Core Insight

The Brain Rot Hypothesis

Continual pre-training on junk web text can cause lasting cognitive decline in LLMs: weaker reasoning, worse long-context performance, lower safety, and inflated dark personality traits.

Why this paper hit me

Most AI discourse still treats more data as free progress. Scrape more. Train longer. Ship the next checkpoint.

This study flips that instinct. The authors take real Twitter/X corpora, build junk and control datasets with matched token budgets, then continually pre-train multiple LLMs under the same training recipe. The only major difference is what kind of text the model keeps eating.

If junk were just noisy but harmless, the junk-trained models should look roughly like the controls. They do not.

Under junk exposure, the models show non-trivial declines (Hedges' g > 0.3) on reasoning and long-context tasks. Safety gets worse. Traits associated with psychopathy and narcissism inflate. Mix junk and clean data in different ratios and you get a dose-response curve: more junk, more decay.

That is the part that should make every AI team sit up. Capability is not a one-way ratchet. Continual training can move the needle backward.

How they defined "junk"

This is where the paper gets clever. "Junk" is easy to say and hard to measure, so they operationalize it two ways.

M1: engagement degree. Think popularity and engagement patterns on Twitter/X. High-engagement content is not automatically insightful. It is often optimized for clicks, outrage, and dopamine. The paper's later forensics even suggest that popularity is a better Brain Rot indicator than length in this setting.

M2: semantic quality. Separate from virality: is the text actually substantive, coherent, and useful, or is it shallow, repetitive, and low-signal?

They keep token scale and training operations matched across conditions. That matters. Without those controls, critics could shrug and say "you just trained less" or "you used different recipes." Here, the comparison is designed to isolate the social and semantic character of the data.

Core Insight

Why the controls matter

Same token budget. Same training operations. Different data diet. That is how you turn a spicy claim into a causal story instead of a vibes take.

The damage is not subtle

Look at the dose-response numbers under M1. As the junk ratio climbs from 0% to 100%:

  • ARC-Challenge with Chain-of-Thought falls from about 72.1 to 57.2
  • RULER-CWE (a long-context stress test) falls from about 83.7 to 52.3

Those are not rounding errors. That is a model quietly losing the ability to reason carefully and hold long context together.

And it is not only "gets worse at quizzes." The safety and personality shifts are the part I keep thinking about after closing the PDF. If junk data can make a model less safe and more dark-traited, then curation is not just a quality-of-life issue for benchmarks. It is a deployment risk.

The smoking gun: thought-skipping

Error forensics are my favorite section of this paper.

The primary lesion is not that models suddenly forget every fact. It is thought-skipping. Models start truncating or skipping reasoning chains. They jump to answers. They abandon intermediate steps. The chain of thought gets shorter, thinner, less careful.

If you have ever watched a tired human skim a hard problem and blurt an answer, you already understand the vibe. The model still produces fluent text. It just stops doing the hard internal work that made the earlier checkpoint look smart.

That distinction is important for builders. A Brain-Rotted model may still sound confident in a demo. Fluency is not cognition. If your evals only check surface polish, you will miss the decay until users feel it in production.

Can you heal it?

Partially. Not fully.

The authors try the obvious recovery moves: more instruction tuning, more clean continual pre-training. Those help. Scores improve. The patient gets better.

But the model does not fully return to baseline. That suggests something deeper than a temporary format mismatch. The paper points toward persistent representational drift. Once junk has reshaped the model's internals, a weekend of clean data does not rewind the tape.

I find that both scientifically interesting and operationally terrifying. It means "we will just fine-tune it later" is not a complete safety plan. Prevention beats cure.

FindingWhy it matters
Junk data causes measurable cognitive declineMore tokens are not automatically better tokens
Dose-response decay as junk ratio risesContamination is gradual, not an all-or-nothing cliff
Thought-skipping is the main lesionModels skip reasoning steps while still sounding fluent
Healing is partialClean data helps, but baseline capability may not fully return
Popularity predicts Brain Rot better than lengthViral engagement can be a toxicity signal for training data

What I am taking into my own work

If you ship LLM features, this paper should change how you talk about data pipelines.

  1. Curate like it is safety work. Continual pre-training on scraped social text is not free progress. It can actively degrade reasoning and safety.
  2. Watch for thought-skipping. Add evals that punish truncated reasoning, not just wrong final answers.
  3. Do cognitive health checks. Before and after every continual training run, re-test reasoning, long context, and safety. Treat regressions as release blockers.
  4. Do not worship engagement metrics. High popularity can mean high signal. It can also mean high Brain Rot potential.
  5. Assume incomplete recovery. If junk got into a training stage, plan for lasting drift, not a quick patch.

This is also why I care so much about evaluation culture at The Grey Project. Demos lie. Holdout tests and regression suites are how you notice a model getting worse while still sounding smooth.

Want a hands-on feel for why prediction quality and eval discipline matter before you trust a shiny demo? Start with our free AI Is Prediction lesson, then dig into tokens and embeddings in Curious Builders.

The bigger story

We already know humans can get cognitively fried by endless low-quality feeds. This paper suggests LLMs are not magically immune. Feed them enough junk, and they start skipping the hard thinking too.

The hopeful reading is also the practical one. If Brain Rot is causal and measurable, then better curation is leverage. Cleaner continual pre-training is not just about higher leaderboard scores. It is about keeping models capable, safer, and less warped by the worst incentives of the open web.

I will be watching follow-up work closely: more platforms, more model families, stronger healing recipes, and better automatic detectors for junk before it enters the training mix. For now, Xing et al. have given the field a phrase worth stealing and a result worth respecting.

Your model can get Brain Rot. Act like it.

References

About the author

Vaibhav Kestikar is a Senior Data Scientist and the founder of The Grey Project. He writes and builds interactive lessons that explain AI systems without hype. Connect on LinkedIn.

Continue learning

Turn this article into intuition

Related lesson: AI Is Prediction, free sample