Search This Blog

Showing posts with label Google Hacks. Show all posts

Google, YouTube, Gmail, Intel Turkmenistan Sites Hacked by Iranian Hackers

Turkmenistan major Sites are defaced by Iranian Hackers yesterday by DNS Poisoning attack. The defaces includes major sites of Google,Youtube,Orkut,Gmail,Intel,Xbox,etc.

These hacked domains are all registered at NIC Turkmenistan. The domain names include


The Hacker just uploaded a simple html page to show off his deface. This is the first attack on NIC sites in 2013. MS SQL Vulnerability lead this to defeat and here is the entire image for it. The hackers have also got access to DNS records.

You can view the entire Data leak from here

Mirrors of Defaced sites can be viewed here

Author of this article: Akshay Kumar.

Guadeloupe Domain provider hacked and Google, yahoo passwords leaked database leaked domain provider database leaked

A hacker called as Ur0b0r0x has made a claim that he gained access to One of the top Domain provider in Guadeloupe. Network Information Center( is the provider of .gp,,, domains .

"Network Information Center Guadeloupe #Hacked #dataleaks  @EHackerNews" The tweet sent to E hacking News reads.
In the paste, he has published few sample data and download link to a 168kb text file that contains the rest of the data.

The leak consists of 1271 account details that contain username, email address and phone number as well as surname. The dump also contains 1238 passwords in encrypted form.

After analyzing the list of data provided, we found that there is data belong to lot of high profile sites including Google, Yahoo and more sites, as they have registered the domain with

The list of high profile sites that has registered domain in this site :,,, Their data can be found in the leak.

We notified the regarding the hack and waiting for their response.

1st security researcher earned $60,000 for Google Chrome hack : Pwnium

Security Researcher Sergey Glazunov, Russia, has been named as the First researcher who earned $60,000 as part of the Pwnium competition run by Google.

He hacked into fully-patched Windows 7 machine (64-bit) by exploiting a remote code execution vulnerability in Google’s Chrome web browser. His hack is qualified as a “Full Chrome” exploit, qualifying for a $60k reward.

This remote code execution vulnerability could be utilised by malicous hackers and cyber-criminals to take control of a user's computer after persuading them to visit a rogue web link.

Sundar Pichai SVP of Chrome and Apps at Google congratulated Glazunov and said :
"We're working fast on a fix that we'll push via auto-update. This is exciting; we launched Pwnium this year to encourage the security community to submit exploits for us to help make the web safer. We look forward to any additional submissions to make Chrome even stronger for our users."
There is Still $940,000 remains in the Pwnium prize fund. 

Google Wallet dropped the support for Rooted Devices

While Google is on the process of fixing the vulnerabilities in Google Wallet, they dropped the Google Wallet support for the Rooted devices.

Last month, Joshua Rubin, a security researcher at zvelo discovered that Google Wallet PIN can be cracked easily by brute forcing on a device that is "rooted". Google immediately confirmed the vulnerability and encouraged users to not install Google Wallet on rooted devices.

Now Google reinforces that recommendation by restricting the Wallet’s installation on rooted devices.

According to the Droid Life report, Google wallet app started showing a little yellow bar at the top along with an “Unsupported device” note over the weekend.
Following the "Learn more" link will direct you to the page which explains the risk of using Google Wallet in rooted devices.

"Some users may disable important security mechanisms in order to gain system-level "root" access to their phone. We strongly discourage doing so if you plan to use Google Wallet. We are unable to support devices with unauthorized operating systems as the security layers of the device may be limited." reads Unsupported Device Policy page.

Google Wallet's PIN System can be easily cracked from rooted devices

Joshua Rubin, a security researcher at zvelo, have discovered that Google Wallet PIN can be cracked easily by brute forcing on a device that is "rooted".

Google Wallet is the first publicly available Near Field Communication (NFC) Payment System that purports to turn to your smartphone into a credit card, allows to purchase by entering a PIN .

In order to facilitate secure transactions,  NFC use hardware component called Secure Element(SE) which is used to store your confidential data such as the complete credit card number.

In order to authenticate users and grant access to the SE, Google Wallet requires a 4-digit, numeric PIN when first launching the app. Unfortunately, the PIN is not stored on the SE , but instead it is stored as a salted SHA256 Hash on the device itself.
"Knowing that the PIN can only be a 4-digit numeric value, it dawned on us that a brute-force attack would only require calculating, at most, 10,000 SHA256 hashes."Joshua Rubin said ." This is trivial even on a platform as limited as a smartphone. Proving this hypothesis took little time."

Google Wallet only allows five invalid PIN entry attempts before locking the user out,but with root access you can bruteforce the PIN without a single invalid attempt.

Rubin concludes that the only way to solve this issue would be to move the PIN verification into the SE itself and to no longer store the PIN hash and salt outside the SE.

Google has issued this statement on the matter:
The Zvelo study was conducted on their own phone on which they disabled the security mechanisms that protect Google Wallet by rooting the device. To date, there is no known vulnerability that enables someone to take a consumer phone and gain root access while preserving any Wallet information such as the PIN.

This confirms that there should be no issue unless your phone has already been rooted. If you have rooted your smartphone, Google strongly encourage you to not install Google Wallet and to always set up a screen lock as an additional layer of security for their phone.(like activating the lock screen, disabling the USB debugging option in settings, and enabling full-disk encryption).

Google Patched High-Risk Vulnerability in Chrome Browser

Google released chrome version 15.0.874.121 that fix the High-Risk Vulnerability in Javascript Engine named V8. This vulnerability is an out-of-bounds error that can cause a memory-corruption condition and lead to remote code execution.

Google paid security researcher Christian Holler $1,000 for discovering and reporting this vulnerability.

Download the Latest Version From here:

Google Maps URL Injection Vulnerability

Google maps is vulnerable to URL Injection(redirects to another page) , discovered by Sony.

Vulnerable Link:


Demo Video:



Can't Believe this: A Hacker called dr@g has Hacked Guadeloupe  Google / Microsoft/ Motorola / Orange / Facebook / Youtube / Myspace / Live / Hotmail / Bing / Visa / Opera / Gmail / Joomla / Ubuntu / Internet / Bank America and Defaced them. The Hacker is in the team called Moroccain Security Cr3w.
Looks like DNS Hijacking(but not sure).

Hacked Site List:


Google+ Hacker Florian Rohrweck Hired By Google for Security

Summary: Thinq reported that Google+ hacker Florian Rohrweck, the source of much pre-release information about Google's social networking service, has announced that he is to join the advertising giant to work on improving the company's security.

Austrian blogger/developer Florian Rohrweck, who discovered unreleased Google+ features by exploring the source code, was hired by Google. Rohrweck's main claim to fame was a period of snooping on the code behind Google's various web apps, during which time he uncovered pre-launch evidence of things like Google+ Games, telling the world of the impending release and somewhat taking the wind of of Google's sails.

Rather than sue him into silence, however, Google has decided to put his talents to good use, hiring Rohrweck to work on improving the security of its various web-based services.

The contract isn't finalised, and Google itself is being cagey on exactly what Rohrweck will be doing at the company. "Get sued or get hired, there is no try, young Skywalker," Rohrweck joked on - appropriately enough - his Google+ page. "Wait, what? Get hired it is."

Rohrweck is expected to visit the Google headquarters in Munich next week, where the team behind Google+ will be eager to see the hacker that's been picking apart their secrets. "I remember, 'let's hire him,' was one of the first reactions when the news you had discovered all those G+ features broke out internally," claimed Google+ team member Marcelo Camelo in a comment to Rohrweck. "Welcome to the team."

Google's decision to hire - rather than scare away - Rohrweck is a good one: not only does the company get access to his not inconsiderable talents, but they get to shut him up with a nice contract at a fraction of the cost of a protracted legal battle.

Rohrweck on his Blog:
Or at least I will be have gone soon. Or something like that :D I will post new articles again. Not so much about leaks but more about the dark arts of mastering Google products and APIs. Or something else. Time will tell!

Thanks to all of you, who supported me on my way and made my work so much fun and enjoyable! You guys are awesome!

Rock on!

DDOS Attack using Google Plus Server-Distributed Denial of Service

R00T.ATI claimed that he found some DDOS vulnerability in Google + on IHTeam Security Blog.  Using this vulnerability, hackers can launch DDOS attack on any other website using the Bandwidth of Google Plus Server.

They demonstrate how an attacker can use the Google Server as Proxy to send request to the target website. Quatrini has written a shell script that will repeatedly prompt Google's servers to make requests to a site of the attacker's choice, effectively using Google's bandwidth rather than their own.

How does it work?

The vulnerable pages are “/_/sharebox/linkpreview/“ and “gadgets/proxy?“
Is possible to request any file type, and Google + will download and show all the content. So, if you parallelize so many requests, is possible to DDoS any site with Google bandwidth. Is also possible to start the attack without be logged in Google

Attack vectors:
The advantage of using Google and make requests through their servers, is to be even more anonymous when you attack some site (TOR+This method); The funny thing is that apache will log Google IPs.
But beware: gadgets/proxy? will send your ip in apache log, if you want to attack, you’ll need to use /_/sharebox/linkpreview/

Pen Tester tried DDOS on his server itself using GOOGLE Plus Server, thread of 1000 requests and the output bandwidth will result in 91/96Mbps (His house bandwidth is only 6Mbps).

Iframe Vulnerability found in Google App Engine

An Indian Hacker "Ethical Mohit" have found in Iframe Vulnerability in Contact Desk page of Google App Engine (Appspot).

#1 Proof of Concept : Click Here
#2 Proof of Concept : Click Here

Google App Engine lets you run your web applications on Google's infrastructure. App Engine applications are easy to build, easy to maintain, and easy to scale as your traffic and data storage needs grow. With App Engine, there are no servers to maintain: You just upload your application, and it's ready to serve your users.Google App Engine makes it easy to build an application that runs reliably, even under heavy load and with large amounts of data.