Panix.com gets hijacked

[Theo]

Story at http://www.panix.net/

Discussions at http://www.merit.edu/mail.archives/nanog/msg04242.html

Also a nice post by our very own GeorgeK :-D
http://forum.icann.org/lists/transfer-comments-a/msg00002.html

 

[Togoodhlth]

Yeah yesterday they were going nuts.
Julian, one of my programmers was helping recapture it.

I guess they have it back though even though Melbourne wasnt open yesterday they were still able to contact them and work something out.

 

[Dave Zan]

Panix.com has been restored...and it appears at record time, too.

 

[Theo]

Panix.com has been restored...and it appears at record time, too.

72 hours is hardly "record time" when the affected domain is an ISP with thousands of customers.

 

[Togoodhlth]

I believe it was hijacked late Saturday and restored late in the day on sunday even though melbourneit is closed on Sunday.
So that does seem pretty damn quick regardless of who the domain was hijacked from.

Glad it worked out for them. Hope they catch the dude who jacked it.

 

[freestyler]

72 hours is hardly "record time" when the affected domain is an ISP with thousands of customers.

agree. :approve:

 

[Togoodhlth]

I believe it was hijacked late Saturday and restored late in the day on sunday even though melbourneit is closed on Sunday.
So that does seem pretty damn quick regardless of who the domain was hijacked from.

How are you guys coming up with 72 hours?
Where I am from there are 24 hours in a day.

Please advise as I hope I am not missing something..

 

[QuantumBeam]

:shy:

 

[DaddyHalbucks]

Sheesh!

Hijacking is becoming a HUGE problem!!

 

[Nexus]

Nexus, umm I am quite sure we all have read that and much more. What's the point of your post? Are you attempting to verify they were down for more than 72 hours? "Most of the weekend" is at best 48 hours.

Sorry if my post was useless. All gone now.

~ Nexus

 

[typeins]

I get dodgy transfer requests all the time.. lucky none of them ever get through.

 

[Togoodhlth]

Nexus, umm I am quite sure we all have read that and much more. What's the point of your post?

Are you attempting to verify they were down for more than 72 hours? "Most of the weekend" is at best 48 hours.

 

[Theo]

The hijack occurred on Friday the 14th. Till the 17th that Panix returned to normal operations, that's 3 days.

 

[DaddyHalbucks]

I wonder how many users/ accounts were effected?

 

[Dave Zan]

The hijack occurred on Friday the 14th. Till the 17th that Panix returned to normal operations, that's 3 days.

True, it's still long considering panix's line of business. But compared to others,
how soon panix.com was restored was quite fast IMHO.

3 circumstances worked in panix.com's favor: Melbourne IT's not sending the
auth email, discovering the new account was created using stolen cc's, and
Melbourne IT having responded quickly despite the slip-up.

I wonder how many users/ accounts were effected?

http://www.pcworld.idg.com.au/index.php/id;2003001350;fp;16;fpid;0]link. But here's the specific:

About 5,000 customers were affected and some of them may have lost 100 or more e-mail messages over the weekend, Rosen said in an interview.

 

[Theo]

Australia is 13+ hours ahead of US Eastern time. Also, DNS propagation for .com domains is much faster now. Given those two factors, Panix was down too long.

 

[Togoodhlth]

"record time" was the amount of time it took MelbourneIT to restore panix.
It was down from Saturday morning/late friday night until Sunday night. Which is no where near 72 hours.
If you include the time it took it to resolve for everyone in the world then yes I would say 72 hours.

BTW, after reading more information about this subject I agree MelbourneIT dropped the ball big time.
Also agree that they need to have 24 hour, 7 day/week customer service. In fact I think it should be mandated by ICANN in the registrar agreement.

Cya'll

 

[Nexus]

BTW, after reading more information about this subject I agree MelbourneIT dropped the ball big time.

Pretty much the point of my previous post (now deleted). You seemed to be pleased with the "quickness" of the correction. I'd sympathize with the frustration of going down as long as it did. I'd criticize ICANN's policy quicker than try to give any nod to Melbourne's timeliness in a weekend crisis situation like this one. I believe the "72 hours" was somewhat laxed short hand for "the weekend", as it seems clear no one is tracking the precise hours of it.

~ Nexus

 

[Togoodhlth]

Pretty much the point of my previous post (now deleted). You seemed to be pleased with the "quickness" of the correction. I'd sympathize with the frustration of going down as long as it did. I'd criticize ICANN's policy quicker than try to give any nod to Melbourne's timeliness in a weekend crisis situation like this one. I believe the "72 hours" was somewhat laxed short hand for "the weekend", as it seems clear no one is tracking the precise hours of it.

~ Nexus

Point taken.
I apologize as it seems that I was receiving bad info from people who were supposedly "in the know".
Frankly I hope this opens someones eyes at ICANN but somehow I dont think it will.

 

[DaddyHalbucks]

ICANN doesn't give a flying fart about such things. They are a big unresponsive bureaucracy.

Only if the whole internet collapsed would they care, and then, only a few weeks or months later.