Posts

The Missing Dirty Bomb that Set Off the Chain of Death

Several days ago, I finished listening to Joby Warrick’s The Triple Agent. It’s quite good, both in terms of readability and news value. But since I have the Audible, not the dead tree, version I wasn’t able to transcribe what I found to be one of the most interesting passages in it.

Luckily, that incident is precisely what he told Tom Ricks he wished people had noticed, so now Ricks has basically transcribed it for me!

BD: What is the one question you’d like to answer about the book that nobody has asked you?

JW: Some of the events in the book have never been described elsewhere, and I’ve been surprised that few reviewers or interviewers have asked about them. One favorite: a description in the book of a dirty-bomb threat that emanated from Pakistan mid-2009 and raised alarms at the highest levels of the U.S. government. Information gleaned through SIGINT intercepts suggested strongly that the Pakistani Taliban (TTP) had acquired “nuclear” material-presumably radioactive sources useable in a dirty bomb–and were trying to decide what to do with it. Concerns over a possible dirty-bomb attack directly factored into the decision to take out TTP leader Baitullah Mehsud, who was killed in a drone strike on Aug. 5 of that year. No radioactive material was subsequently found, and to this day, no one knows what happened to it, or indeed, whether it ever existed.

As Warrick revealed, the reason we were so intent on taking out Mehsud is because of intelligence that he might have the radioactive material for a dirty bomb (IIRC, the CIA was responding to SIGINT they deemed to be code). As tends to happen when we use uranium to justify war, no nukes were found.

A pity for Mehsud’s young wife, who also died in that attack (Warrick describes how they died on their rooftop in some detail).

I raise this not just to recommend Warrick’s book. But to remind you how our government decided to claim the retaliation for this drone strike by Mehsud’s brother was a crime, presumably because the escalating series of revenge ended in Humam al-Bawali’s Khost attack.

But the mention of CIA’s drone campaign in Pakistan raises a bunch more problems with DOJ’s charges. For starters, Mehsud’s wife–a civilian–was reportedly killed in that January drone strike too. Both the uncertainty the CIA has about its purportedly scalpel-like use of drones and the civilian deaths they’ve caused illustrate the problem with drones in the first place. Civilians–CIA officers–are using them in circumstances with significant collateral damage. It would be generous to call the use of drones in such situations an act of war; some legal experts have said the CIA officers targeting the drones are as much illegal combatants as al Qaeda fighters themselves.

The affidavit describing the evidence to charge Mehsud doesn’t say it, but underlying his alleged crime is the potential US crime of having civilians target non-combatants in situations that cannot be described as imminently defensive.

Charging someone for revenge on CIA’s illegal killing

Which leads us to the crimes for which they’re charging Mehsud: conspiracy to murder and conspiracy to use a WMD (bombs) against a US national while outside of the United States. Basically, DOJ is charging Mehsud with conspiring with Humam Khalil Mulal al-Balawi, the Jordanian doctor who committed the suicide bombing at Khost that killed 7 CIA officers and contractors.

Now, there’s not much doubt that Mehsud did conspire with al-Balawi. I just doubt whether it could be fairly called a crime. The affidavit describes two videos in which Mehsud stands side by side with al-Bawali. In one, both al-Balawi and Mehsud describe the upcoming attack as revenge for killings in the drone program–most importantly, of Mehsud’s brother Baitullah Mehsud from a CIA drone strike in August 2009.

Al-Balawi then continues alone: “This itishhadi [martyrdom-seeking attack] will be the first of the revenge against the Americans.” After additional declarations of revenge by al-Balawi, MEHSUD resumes speaking in Pashtu, explaining the motive for the upcoming suicide attack by al-Balawi, that is the death of the former emir of the TTP, Baitullah Meshud [sic] which MESHUD [sic] attributes to the Americans.

Remember, too, that al-Balawi was a double agent. The Americans believed he was helping them target people, people just like Mehsud. That means al-Balawi (and presumably through him, Mehsud) knew he was specifically targeting those behind the earlier killings in Pakistan when he killed them.

So al-Balawi successfully killed people who were either civilians, in which case their own strikes at Baitullah Mehsud and others may be illegal, or people who were acting as soldiers, in which case the attack on their base was presumably legal under the law of war. And for helping al-Balawi, DOJ is now charging Mehsud with conspiracy.

The affidavit, of course, neglects to mention any of these details.

Let me be clear: the Administration’s stupid attempt to apply this double standard doesn’t make the Khost bombing any less tragic. But it did strike me as a pathetic attempt to cloak a disastrous blood feud, for all sides, in legal niceties to somehow make it seem like something else.

But I find it all the more ironic that the whole blood feud was triggered with yet another nuke claim that may have been wrong.

Look Forward, and Promote the Torturers

There’s Matt, who froze Gul Rahman to death in the Salt Pit. Paul, his boss and the CIA Station Chief of Afghanistan, who ignored Matt’s requests for more help at the prison. There’s Albert, who staged a mock execution of Rahim al-Nashiri, and his boss, Ron, the Station Chief in Poland, who witnessed the forbidden technique and did nothing to stop it. There’s Frances, the analyst who was certain that Khaled el-Masri had to be the terrorist with a similar name, and Elizabeth, the lawyer who approved Frances’ decision to have el-Masri rendered and tortured. There’s Steve, the CIA guy who interrogated Manadel al-Jamadi and, some say, effectively crucified him. There’s Gerry Meyer, the Baghdad station chief, and his deputy, Gordon, who permitted the ghost detainee system in Iraq. And of course, there’s Jennifer Matthews, the Khost station chief who ignored warnings about Humam Khalil Abu-Mulal al-Balawi that might have prevented his attack (and her own death).

These are the CIA officers responsible for the Agency’s biggest known fuck-ups and crimes since 9/11.

The AP has a story tracking what happened to those officers. And it finds that few were held accountable, particularly not senior officers, and even those who were reprimanded have continued to prosper in the agency.

In the years since the Sept. 11, 2001, terrorist attacks, officers who committed serious mistakes that left people wrongly imprisoned or even dead have received only minor admonishments or no punishment at all, an Associated Press investigation has revealed.

[snip]

Though Obama has sought to put the CIA’s interrogation program behind him, the result of a decade of haphazard accountability is that many officers who made significant missteps are now the senior managers fighting the president’s spy wars.

The AP investigation of the CIA’s actions revealed a disciplinary system that takes years to make decisions, hands down reprimands inconsistently and is viewed inside the agency as prone to favoritism and manipulation. When people are disciplined, the punishment seems to roll downhill, sparing senior managers even when they were directly involved in operations that go awry.

Paul–the guy who let the inexperienced Matt freeze Gul Rahman to death–is now chief of the Near East Division.

Ron–who watched Albert stage a forbidden mock execution–now heads the Central European Division.

Albert–who staged the mock execution–was reprimanded, left the CIA, but returned to the CIA as a contractor involved in training officers.

Frances–who insisted Khaled el-Masri be rendered and tortured–was not disciplined and now heads the CIA’s “Global Jihad” unit.

Elizabeth–the lawyer who approved el-Masri’s rendition–was disciplined, but has since been promoted to the legal adviser to the Near East Division.

Steve was reprimanded–not for his interrogation of al-Janabi, but for not having him seen by a doctor. He retired and is back at CIA as a contractor.

Gordon–the Deputy at the Baghdad station at the time of the worst torture–was temporarily barred from working overseas and sent to training; he’s now in charge of the Pakistan-Afghanistan Department of the Counterterrorism Center.

And, as the AP notes, several of these people are now among Obama’s key counter-terrorism advisors. (Of course, John Brennan, who oversaw targeting for Dick Cheney’s illegal wiretap program, is his top counter-terrorism advisor.)

No wonder Obama has no problem pushing our Egyptian torturer, Omar Suleiman, to lead Egypt. It’s completely consistent with our own practice of promoting our own torturers.

CIA and DOJ’s Different Ideas of Accountability on Khost

I wanted to return to yesterday’s report on the investigation in the Khost bombing. As I noted, the CIA had advance warning that Humam Khalil Abu-Mulal al-Balawi might be a double agent. The report also found a number of other operational problems in al-Balawi’s treatment. But Leon Panetta decided not to hold anyone responsible for the attack.

Now let’s return to another curious detail about the Khost bombing.

The CIA is not holding anyone responsible.

But DOJ is.

As I noted last month, DOJ is using Hakimullah Mehsud’s involvement in the Khost bombing–the DOJ has videos of Mehsud talking about the attack with al-Balawi in advance of the bombing–as its basis for indicting him on conspiracy charges.

It’s not that I mind DOJ indicting Mehsud. They say they’ve got evidence linking him to Faisal Shahzad’s attempted Time Square bombing. And if they do, I’d love to see them indict and try Mehsud on that count.

But it’s a tremendous stretch to argue that Mehsud’s conspiracy with al-Balawi to strike the CIA officers who were targeting Pakistan with drone strikes was illegal. Either the CIA officers must be treated as civilians, in which case they should not be launching drones at people like Mehsud’s brother, whom they killed in a drone attack. Or they are legitimate military targets, in which case any involvement from Mehsud seems to have been a legitimate act of self-defense (hell, regardless of their civilian status, he could probably legitimately claim self-defense in any case).

Mind you, they’ll probably end up taking Mehsud out the same way the took his brother, with a drone, making any indictment moot. But it all seems to suggest that at its higher levels, at least, we’re running this war on terror motivated primarily by our own insecurities, latching onto things that most shame us, rather than any consistent approach. We’ve got to avoid accountability at CIA for some obvious failures because we don’t want to be critical of the dead (or note the mistakes of more senior officers). But we’ve got to use the same event as reason to label the self-defense of an opponent as a crime.

Which seems to be the same thing going on with Fox’s story that Anwar al-Awlaki dined at the Pentagon after 9/11 (at a luncheon in Jim Haynes’ Office of General Counsel!). The fear-mongerers seem to want to suggest this was another big lapse in our vetting system (and maybe it was), as if to suggest that al-Awlaki in 2001 is in the same place he allegedly is now. The FBI was investigating this lunch subsequent to Nidal Hasan’s Fort Hood attack (the 302 is dated November 23, 2009, so at about the time when Yemen asked us to take out al-Awlaki, but probably before he was reportedly put on JSOC’s kill list, which may have happened in December). And leak of this news seems to be part of an effort to suggest the government missed an obvious threat long before Fort Hood. But that’s not at all clear.

CIA Had Warning on Khost Attack, Will Not Hold Anyone Responsible

Jordanian intelligence warned the CIA that Humam Khalil Abu-Mulal al-Balawi, the Khost bomber, might be working for al Qaeda three weeks before al-Balawi killed 7 CIA people in the attack. But because the CIA still suffers from the same information sharing shortcomings problems that prevented it from finding out about 9/11, the CIA still allowed al-Balawi onto their forward operating base.

Three weeks before a Jordanian double agent set off a bomb at a remote Central Intelligence Agency base in eastern Afghanistan last December, a C.I.A. officer in Jordan received warnings that the man might be working for Al Qaeda, according to an investigation into the deadly attack.

But the C.I.A. officer did not tell his bosses of the suspicions — brought to the Americans by a Jordanian intelligence officer — that the man might try to lure Americans into a trap, according to the recently completed investigation by the agency.

But the CIA is not holding anyone responsible for this horrible lapse, partly because the station chief killed in the attack would have received much of the blame.

Mr. Panetta said that the report did not recommend holding a single person or group of individuals directly accountable for “systemic failures.”

“This is a war,” he said, adding that it is important for the C.I.A. to continue to take on risky missions.

[snip]

Current and former C.I.A. officials said that the decision not to hold officers directly responsible for the bombing was partly informed by an uncomfortable truth: some of them might have been among those killed in the bombing.

The officials said there was particular sensitivity about how much fault to assign to Jennifer Matthews, a Qaeda expert who was the chief of the Khost base.

Before you accept that explanation, re-read the piece that Bob Baer wrote on the Khost killing in April. He attributes the lapses to the de-professionalization of operations within CIA, and argues that Matthews (whom he calls Kathy) was set up to fail.

On January 10, 2010, CIA director Leon Panetta wrote a Washington Post op-ed in which he disputed that poor tradecraft was a factor in the Khost tragedy. Panetta is wrong.

An old operative I used to work with in Beirut said he would have picked up Balawi himself and debriefed him in his car, arguing that any agent worth his salt would never expose the identity of a valued asset to a foreigner like the Afghan driver. I pointed out that if he’d been there and done it that way, he’d probably be dead now. “It’s better than what happened,” he said.

One thing that should have raised doubts about Balawi was that he had yet to deliver any truly damaging intelligence on Al Qaeda, such as the location of Zawahiri or the plans for the Northwest bomb plot. Balawi provided just enough information to keep us on the hook, but never enough to really hurt his true comrades. And how was it that Balawi got Al Qaeda members to pose for pictures? This should have been another sign. These guys don’t like their pictures taken. So there were a few clear reasons not to trust Balawi, or at least to deal with him with extreme caution.

But the most inexplicable error was to have met Balawi by committee. Informants should always be met one-on-one. Always.

The fact is that Kathy, no matter how courageous and determined, was in over her head. This does not mean she was responsible for what happened. She was set up to fail. The battlefield was tilted in Al Qaeda’s favor long ago—by John Deutch and his reforms, by the directors who followed him, by the decision to drop the paramilitary course from the mandatory curriculum (which would have made Kathy a lot more wary of explosives), and by two endless wars in Iraq and Afghanistan that have worn the CIA down to a nub. Had Kathy spent more time in the field, more time running informants, maybe even been stung by one or two bad doubles, the meeting in Khost probably would have been handled differently—and at the very least there would have been one dead rather than eight.

And while two of the recommendations Leon Panetta offered in response to the investigation was to provide more training on counterintelligence and to make sure veterans are involved in the most critical counterterrorism operations, that doesn’t address what Baer, at least says needs to happen: fixing the entire career path of CIA professionals out in the field.

Is not holding anyone responsible for this horrible mistake about protecting a CIA officer who died after being set up to fail? Or protecting her superiors who put her in that position?