Mika's OGR page shows a HUGE spike

[JonB]

Now even more of the OGR Proxies are showing HUGE numbers.

Something is still hosed

 

[Russ]

Holy crap. Those numbers look even higher than they did the other day.

Russ, NCNE

 

[Dutchman2000]

Well one distributed person told me a while back that over 50% of all submitted OGR work comes from worms, and that they have over 250.000 different IP adresses submitting worm-data. This shouldn't show up in the stats etc. because dnet is banning them (naturally). Maybe now the OGR rate shoots up because of the problems with stats-box ii is causing the ban to fail. (just a guess ofcourse)

 

[MTP]

OR:

We can always hope that someone has been saving up OGR packets since the contest started, and they finally ran out of hard drive space to store the Buff-out 😉

 

[NT4Mike]

Must have been a datacenter 😛

-Mike

 

[sciencewhiz]

Well, I figure that 9 exanodes is about 15,000,000 mhz of PIII power. This couldn't have been a problem with the stats box becuase they showed up at the team pproxy, and several of the dnet proxys are showing huge spikes as well.

I don't think this could be a trojan either. This is only a one-time dump. Unless there is a smart trojan that changes the e-mail addresses, or shuts down after a certain period of time, it wouldn't be possible to have a single huge spike like that.

The blocks also all come from one IP (right?). I guess someone could be hoarding trojaned (or real) blocks and finally flushed them. If they held for the entire 90 days or so that OGR 25 has been running, you would only need 166 1 ghz PIIIs, which is possible.

The last option is someone hacked the client so that it can submit bad results. I think this is the most likely scenario, but probably one of the hardest to clean up after.