How the FBI Blew Its Own Cover in Counter-Terrorism Sting


The FBI had been onto suspected ISIS-wannabe Everitt Jameson for weeks. Court documents say that following a tip from an informant, the feds had seen the California tow-truck driver “liking” and “loving” terrorism-related content on social media. They arranged for Jameson to unwittingly meet with an undercover agent, where he praised jihadists and deadly terror attacks.

Eventually, he turned the corner and allegedly sketched out his own plan to detonate a bomb and gun down innocent civilians in San Francisco — maybe on Christmas Day for maximum effect. He would not need an escape plan, he purportedly said, because he was ready to die.

Related: Infiltrating a Jihadist Cell to Defend America... And Islam (RealClearLife)

Then, on Dec. 18, a week before the proposed attack and at perhaps the most tense part of the sting operation, a fumble.

“[A]n FBI employee, using an identifiable telephone number with a Washington, D.C. area code (202) mistakenly called Jameson’s cellular phone. After Jameson answered in apparent Arabic language, the FBI employee immediately terminated the call. Shortly afterward, Jameson called the 202 telephone number, which resolves to a voice mail identifying the name (but not employing agency) of [the] user of the 202 telephone,” a criminal complaint in the case says.

It wasn’t much, but it was apparently enough to spook the FBI’s quarry...

Read the full story over at

[Do you have a tip or question for Code and Dagger? Reach us at And if you like what you read and want to help keep the site running (kind of) smoothly, click here to learn how you can support the site. ]

DHS Secretary Says She Didn't Hear Trump's Alleged 'S***hole' Remark

5 Government IT Projects That Were Multi-Multi-Million-Dollar Failures