What We’ve Learnt From the Benthall Criminal Complaint?
Posted by: Allen Hoffmann, JD
January 2, 2015
New York is still leading the charge on dark markets, and it’s a joint effort of the Federal Bureau of Investigations, Homeland Security Investigations, and the Drug Enforcement Administration – Benthall criminal complaint, page 6 and elsewhere.
The special agent who is making the criminal complaint is attached to a cybercrime squad working out of the FBI’s New York field office, and states that they are working a joint investigation with HSI. During September and October of 2014, as a component of the investigation, the DEA used a Manhattan address to order heroin, cocaine, LSD and oxy to help build the case.
HSI had an undercover operative in SR2 since day one, and they were a mod or admin, trusted by defcon, and on the payroll, who could see the user support interface – Benthall criminal complaint, page 6 onwards.
The complaint emphatically indicates that Homeland Security Investigations had an undercover operative, not an informant, but rather, an actual undercover HIS officer working in the administration team of SR2; in fact, s/he was INVITED to become a mod on October 7, 2013, in the wake of the SR 1 takedown [sidebar: as soon as one investigation winds down, major agencies engaged in task forces such as those assembled for SR 1 have two options; go back to their normal duties or find a new target before momentum is lost. Guess which way this went?] during recruitment of vendors from SR 1. It is not unreasonable to assume, considering the trust being placed in the HSI’s UC, that s/he was, potentially, a known and trusted vendor at SR1. At page 15, discussions visible only to mods and admins (a group which the HSI belonged to) occurring on July 15, 2014 are reproduced. At page 18, excerpts of a conversation between defcon and the HSI UC about reestablishing SR2 in the wake of the BTC thefts is reproduced. It is not unreasonable to assume that defcon must have regarded the HIS UC rather highly to have such discussions- and its no wonder, considering that at page 18, we hear that the UC has been paid the equivalent of 32k since January 2014 for admin duties. Finally, at page 27, we learn the UC was able to gather information about OS and browser information used to access the site (more on this later in the article)
Author’s observation:
Defcon didn’t recruit the HSI UC; that falls on DPR2, who was running SR2 for a couple of months. You’re only as good as the weakest link, and this is the absolute worst case scenario. DPR2, before he departed the scene, managed to invite a fox into the henhouse from day one of their operation’s establishment.
Defcon was receiving potentially spurious counter-intelligence information – Benthall criminal complaint page 19-20,
On January 2, 2014, Defcon claims to have acquired intelligence about a ‘darknet’ related operational deployment of FBI SAs to MN, and that vendors in that region need to enhance their security. Defcon specifically notes that the source of this information had been correct before, but had been late to the party.
Author’s observation:
Intel information which you get after the fact is not much good to prove that you’re either connected enough to know what’s going on, or that the provider wanted you to act on it. Police maintain intelligence units, and accordingly, also maintain counter intelligence units. Its not at all unlikely that this information which, whilst correct, arrived late, was part of the effort to help bolster the criminal complaint against defcon – sacrificing outdated information is not sacrificing anything at all. LE is notorious for covering up intelligence leaks (if they don’t report themselves, no one will ever detect their screw up, so its not in their interest to highlight this sort of thing); if this were not a set up or fabrication, the details would NEVER make it into an indictment, much less a criminal complaint such as this.