SQL Slammer Clean-up: How to Report

Published: 2010-10-04
Last Updated: 2010-10-04 00:50:30 UTC
by Kevin Liston (Version: 1)
3 comment(s)

Hopefully you've read the kick-off (http://isc.sans.edu/diary.html?storyid=9637) and have looked at bit at your logs. Perhaps you've worked out what the cost of slammer is to your network on the back of a npkin. In most instances it probabably would cover the price of your lunch, or it's enough to justify the small amount of time this exercise will cost you.

Create a simple spreadsheet listing the IP addresses that have been hitting your perimeter. You'll want to track who the abuse contacts for that network are, when you send your notice, and what kind of response that you get (we'll add more columns later this week.)

Next you'll be running a few WHOIS requests. Everyone has a favorite way to do this (send in your comments on what you think is the easiest way pull abuse contact information.) Depending on your resources, you may have time to tackle all of them, others may only have time to do handle 25 or so. Everyone should try at least ten, if only to get a good sample of the different types of response that you get from your first efforts. Just remember that there are a lot of people doing this along with you this month.

When you compose your first message I want you to keep a few things in mind:

  • Be polite and professional-- you are trying to enlist the help of a stranger. Take a look at some of the emails that come into your abuse contact email if you have access. Mimic the alerts that you respond positively to, avoid the behaviors of those you dislike.
  • Provide logs-- if you don't initially provide logs, that will be their first request of you. Demonstrate that you're on the level with your first message and set them up to succede. It's ideal to provide the logs in GMT, but if that's not convenient, provide the GMT offset for your logs. There is no shame in getting probed/scanned on your perimeter, so there is very little to hide from them.

Feel free to cite these diary entries or use us as a reference. Tom Liston has other (humorous) tips on how to make an abuse report here: http://isc.sans.edu/diary.html?storyid=9325

Take a few minutes to reach out. Statistically-speaking, you're most likely to get no response or an error message (we'll cover how to proceed in those cases later,) so don't be daunted or give up because of that.


Keywords: slammercleanup
3 comment(s)


Re: whois &c; I like robtex (www.robtex.com/) for digging into all sorts of details of an IP or of a domain. Use it a lot since the !@#^ security guys have straight whois blocked.
At the moment I am a fan of abusix.org (goto: "what we do"). Very nice scriptable.

And: I am a fan of "nfsen". Still working on my script/blog.
abusix.org looks like it will be a very useful service when it comes out of beta, however at the moment the data appears to be somewhat stale.

Just this morning I was reporting Slammer activity from, and "whois" reports different (and presumably fresher and more accurate) results than "dig +short txt" does.

That said, I sincerely hope abusix.org irons out all the warts - for automated abuse reporting I would _much_ rather do a DNS TXT query than doing a whois lookup and parsing the results.

My current TCP tarpit report:
23/tcp: 1 host(s), 1 connection(s)
1080/tcp: 1 host(s), 1 connection(s)
1433/tcp (MSSQL): 3 host(s), 1269 connection(s)
2967/tcp: 1 host(s), 4 connection(s)
3389/tcp: 3 host(s), 11 connection(s)
4899/tcp: 1 host(s), 1 connection(s)
5900/tcp: 1 host(s), 1 connection(s)
8080/tcp (PHP scans): 1 host(s), 1 connection(s)
8081/tcp (referrer spam): 1 host(s), 8 connection(s)

Diary Archives