DNSChanger IP address standoff a legal lesson for botnet fighters

  • Liam Tung (CSO Online (Australia))
  • — 22 August, 2012 09:42

The response to DNSChanger malware achieved unprecedented cooperation across the globe, but an ongoing scuffle over takedown procedures highlights challenges for future coordinated US-European take-downs.

This week European IP address registry RIPE NCC reallocated two IP address blocks previously used by Rove Digital, the Estonian company charged with operating a large click fraud operation associated with the DNSChanger malware.

The Netherlands-based registry last November “locked” four IP address blocks to prevent registration details being altered and meet an order by the Dutch Public Prosecution at the behest of the FBI, which was running “Operation GhostClick”.

RIPE this January opted to “unlock” those blocks and last week reallocated them, surprising some in the DNSChanger Working Group (DCWG), which spearheaded the global DNSChanger cleanup.

“Once [RIPE NCC] had locked the blocks we figured they would sit on them. That was the assumption,” Barry Greene, a contributor to DCWG and the former president and CEO the Internet Systems Consortium (ISC) told CSO.com.au.

“There’s a lot of irritated people right now,” he said, including in law enforcement, security researchers and the internet industry.

For a year until July 9, ISC was responsible for DNS servers that connected to those IP blocks to ensure DNSChanger victims could continue connecting to the internet.

Greene said there is a risk the reallocated IP address blocks could be used by their owners to hijack the computers of DNSChanger victims, but noted that in practice this is unlikely since they’re filtered by nearly all major service providers.

The bigger threat he sees is to other groups working on disrupting malware with a much larger cost to society, such as Zeus.

“My concern is how other working groups I’m not a part of [will be affected] -- and there’s a lot of them out there who are working on cyber criminal operations that have a bigger economic impact against society,” Greene told CSO.com.au.

RIPE NCC is heading to court in November to clarify whether it needs to comply with the type of order it initially faced. Pending the outcome, the next group that wants to achieve a similar result may need to request a tougher order from Dutch authorities to confiscate relevant blocks.

“That’s going to be controversial when someone goes through with the Dutch authorities and sets up a confiscation order,” said Greene, noting that it was one option the FBI chose not to pursue this time.

Follow @CSO_Australia and sign up to the CSO Australia newsletter.

Comments are now closed.
CSO Corporate Partners
  • Webroot
  • Trend Micro
  • NetIQ
rhs_login_lockGet exclusive access to CSO, invitation only events, reports & analysis.
CSO Directory

Email Security and Data Protection

Encrypt your sensitive email

Security Awareness Tip

Incident handling is a vast topic, but here are a few tips for you to consider in your incident response. I hope you never have to use them, but the odds are at some point you will and I hope being ready saves you pain (or your job!).


  1. Have an incident response plan.

  2. Pre-define your incident response team 

  3. Define your approach: watch and learn or contain and recover.

  4. Pre-distribute call cards.

  5. Forensic and incident response data capture.

  6. Get your users on-side.

  7. Know how to report crimes and engage law enforcement. 

  8. Practice makes perfect.

For the full breakdown on this article

Security ABC Guides

Warning: Tips for secure mobile holiday shopping

I’m dating myself, but I remember when holiday shopping involved pouring through ads in the Sunday paper, placing actual phone calls from tethered land lines to research product stock and availability, and actually driving places to pick things up. Now, holiday shoppers can do all of that from a smartphone or tablet in a few seconds, but there are some security pitfalls to be aware of.