[UPDATE (1224PM)]: google.com.my is now accessible but not for google.my.
[UPDATE (1130AM)]: For those who are interested on how the DNS poisoning was detected and confirmed, this is an informative and step-by-step look it by by local web consultant company, Localhost Sdn Bhd. It is written in Bahasa Malaysia though.
[UPDATE (1043AM)]: MYNIC Berhad – the national administrator of .my domains – have released their own statement in reference to the incident as well.
[UPDATE (1024AM)]: Google Malaysia have released a brief statement regarding the incident. The manager for Google Malaysia’s domain have also shared the timeline of the incident.
[UPDATE (1009AM)]: While the google.com.my and google.my URLs are still not accessible, they no longer rerouted to the hacker’s page as the name servers have been restored to Google’s own.
[UPDATE (922AM)]: TeaM MADLEETS have released further statements such one on their Facebook and another to TechCrunch.
[UPDATE (317AM)]: Both domains are still affected by DNS poisoning. Meanwhile, we have contacted both Google Malaysia and MYNIC for their official comments regarding this incident. We hoping to hear the official side of the story from them later today.
[UPDATE (231AM]: A thread in the Kopitiam section of Lowyat.NET Forums has indicated that this incident might have been set in motion since few hours ago. Follow the whole progress of this incident at the thread right here.
[UPDATE (220AM)]: Apparently, TeaM MADLEETS have been responsible for DNS poisoning on several other Google domains last month – 1, 2.
[UPDATE (211AM)]: The proud claim by TeaM MADLEETS on their Facebook page after successfully redirected Google Malaysia’s domains.
[UPDATE (200AM)]: Here are some proof of DNS poisoning on Google Malaysia’s domain that was done by TeaM MADLEETS, as compiled by Evozi Plus.
Original story:
It has come to our attention that Google Malaysia’s site has been hijacked by a group of hackers that called themselves TeaM MADLEETS which seems to be based or originated from Pakistan. To certain extent, this latest hijack incident mirrors to the one that took place back in July although the scope seemed to be limited to google.com.my and google.my for now.
We are actively looking for more clarification on this incident, so expect further updates coming your way very soon.
[Source: Evozi Plus]
