Web Honeynet Project IDs Attackers
narramissic writes "The Web Honeynet Project, an independent group of Honeynet researchers from Securiteam and the ITOSF, is putting a new twist on Web application honeynets by naming not only the attack details, but the IP addresses and other tracking information about the attackers as well. As security consultant Brent Huston notes, 'This approach is not unheard of, as lists of known high-volume attackers have been circulating through the Net for several years, but this is the first time someone has applied the honeynet concept to making attacker IP data publicly known.'"
I wonder if it's just a matter of time before someone sues them for defamation. But still a good thing they are doing. the more pressure on spammers the better.
meep
Place a PF firewall in front of your core routers (FreeBSD, NetBSD, OpenBSD) and add this:
block in drop quick on $ext_if proto {tcp, udp} from any to any os Windows
Glass
Think of this as a first step. Next more honeynets start making lists, and a new realtime blackhole routing list is born! Stop the botnets at the gates of the core. More bandwidth for everyone, and the people cut off will get the hint to fix/patch the damn PC!
I looked for the data mentioned in the summary and all I could find was this from the Securiteam blog (posted Jan 12). Is that it? Interestingly it says the name of the project has been changed from "Web Honeynet Project" to "Web Honeynet Task Force".
I see we have some rather humour-deficient mods in the house tonight.
This may just exacerbate the botnet issue. Think about it; if most attacks are relayed through bots, and bots are vulnerable Windows machines, then this kind of effort is only publicizing lists of IPs where vulnerable Windows machines reside.
That sounds like a dream-come-true for attackers.
tasks(723) drafts(105) languages(484) examples(29106)
Unlikely. Its more like they ID the comprised machine the attacker is using.
Bad idea.
---- Booth was a patriot ----
BUT there is a chance that the local law enforcement can put a sniffer on that connection at the ISP level and track the connection that way.
The major problems with that is
#1. Coordinating law enforcement efforts in various countries
#2. Educating the enforcement agencies in those countries
#3. Finally busting the cracker
Even if all of that was accomplished, there would be another zombie master along in a few days to take over the vulnerable machines that are left behind.
http://www.dshield.org/ collaboratively collected ip addresses that were showing up in log files. At first you could search broadly but probably due to the various worms with backdoors such as CodeRed, they switched it to just looking up 1 ip address at a time.
If you need text styles to communicate then you don't have a message.
I signed up at http://www.projecthoneypot.org/ for a similar type of aservice last year. This one is a distributed system for identifying spammers and the spambots they use to scrape addresses from your website.
This one shows Harvester Visits to Your Site(s), email Addresses Issued on Your Site(s), Spam Received at Your Addresses, and global statistics. They also show an ip list from harversters and track it.
Think about it; if most attacks are relayed through bots, and bots are vulnerable Windows machines, then this kind of effort is only publicizing lists of IPs where vulnerable Windows machines reside.
Not a problem. When 50 or so botnet herders all try to use the same pasture, the overgrazing will kill it off. Problem of zombies is solved as they melt down.
The truth shall set you free!
I wonder how effective this can really be. I get a lot of traffic on my server from clients that may be attempting to DOS me, or may just be running poorly behaved webscraper scripts, e.g., scripts looking for blogs and wikis they can spam, which end up requesting the same large URL three times in one second. So far I've been able to keep them from giving me a lot of downtime, through a combination of mod_evasive and some homebrewed scripting. When I do a reverse DNS on them, they typically look like they're just DHCP-assigned IP's from U.S. or overseas ISP's. Most likely many of these are zombie machines that are part of a botnet. I don't see how maintaining a blacklist of IP's is going to help, since they'll just be doing it from a different IP tomorrow.
Find free books.
I must be in the brainless zone today. I cannot find this highly publicized and promoted list of IP numbers. We got articles, we got links, but IP numbers? Ogg not find. Ogg feeling stupid. Embarrass family. Ogg need know if his IP number on list, even though he regularly change router's WAN ethernet number, get new IP from glomcast. Ogg spend much time nmapping spammers. Running nessus. Ogg probably on someone's list as troublemaker. Ogg not care. Tired of UEC not from wild boar.
The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
http://www.webappsec.org/projects/
This project is already gathering data and will be publishing the results shortly.
Believe me, if I started murdering people, there would be none of you left.
I'm one of those people who could be hosting a bot and not even know it. (Just for the record, I try to make sure I don't, but I have no guarantees of success.) I'd really LIKE a system that turned off the traffic WITH A WARNING MESSAGE ABOUT WHY. I could understand if they didn't tell me how to fix it, since that would presumably differ on different systems. It would be a relief to know that in spite of my ignorance, I didn't have to worry about being part of the problem.
This is from the EFF, giving good guidelines on what constitutes defamation.
Note that what makes this really tricky for the online world is that in most cases defamation is a state matter, not a Federal one, making jurisdiction a tough issue. Different states have different qualifications for defamation, one of the most relevant being whether or not the defendant knowingly made false statements about the plaintiff.
As an example, note the qualifications for defamation in Minnesota
I'll believe it when I see it.
More likely, botnet software will start incorporating anti-malware functionality targetting competing bots.
tasks(723) drafts(105) languages(484) examples(29106)
Every time someone spams/annoys/generally pisses me off I add them to a block list
http://fu.ckers.org/fuckers.txt
I work at a pretty large multi-national and I have talked with the lawyers about honeypots from time to time and basically they are divided amongst themselves of if the honeypots are even legal to begin with. One of them is convinced that a honeypot is entrapment.
These guys are already doing this via web honeypot and pushing in real time the IP list to our firewall. http://www.autoshun.org/ It updates on the fly depending on the threat. Makes me sleep better at night.