FBI added Anonymous hacker Jeremy Hammond to a terrorist watchlist several months before the Stratfor hack and his arrest
Context & Ripple Effects
The Hammond revelation lands amid a string of Techdirt-era stories about how the FBI handles politically motivated hackers: leaked documents showed the bureau sat on a hacker's identity in the Matthew Keys case for at least two years without charging anyone, while agents separately spent time running down a Tennessee man who merely copied the Sony attackers' Pastebin style. The through-line is an FBI that treats hacking as a national-security problem first and a criminal one second.
Placing Hammond — an Anonymous figure tied to the Stratfor breach — on a terrorist watchlist before the hack and arrest extends that posture from investigation into pre-emptive designation, a categorization the bureau has since pushed further with domestic-extremism framings around tech-adjacent actors.
First-order effects
- Hammond was designated a terrorist threat before the Stratfor intrusion he was ultimately arrested for, meaning the watchlist system captured him ahead of any prosecutable act rather than as a consequence of it.
Second-order effects
- Other Anonymous-affiliated and even stylistic imitators — like the Tennessee Pastebin copycat the FBI interviewed — now fall inside a surveillance perimeter built for terrorism, widening who gets watched regardless of whether charges ever follow.
Third-order effects
- If the pattern holds, 'hacker' quietly becomes a terrorism category: the same logic resurfaced when DHS and the FBI introduced 'anti-tech violent extremism' as a named domestic threat class, institutionalizing what the Hammond watchlisting did ad hoc.
The trend: US law enforcement is progressively reframing politically motivated hacking from crime to terrorism, with watchlists and threat designations preceding prosecutions.