GOOGLE MALAYSIA DEFACED BY PAKISTANI HACKERS

The Google Malaysia domains google.com.my and google.my have been defaced by hackers of the Pakistani Madleets group. This appears to be yet another case of DNS hijacking.

Over the past period, a lot of hacker groups have leveraged DNS poisoning to make it look like high-profile websites have been defaced. Team Madleets is a collective that has often used this technique.

The hackers have clarified on Facebook that the attack is not “the result of any kind of hate.”

“We don't hate anyone, We love all humanity, there is no obvious reason for stamping the tlds. Least the reason is not any kind of hate. Whatever the reason is we can't explain except we love all of you,” they stated.

It’s worth noting that this isn’t the first time when high-profile domains from Malaysia are defaced via DNS hijacking. A few months ago, Bangladeshi hacker Tiger-M@te defaced Microsoft, Dell, Skype, Kaspersky, MSN and Bing domains.

At the time, Malaysian domain registrar MYNIC admitted being breached.

Piercing Through WhatsApp’s Encryption

WhatsApp has been plagued by numerous issues in their security: easily stolen passwords, unencrypted messages and even a website that can change anyone’s status. But that streak is not yet over.

To be clear: this post is not about using IMEI numbers as your password. That issue has been fixed. Logging in on a new device currently works as follows:

• The phone posts its phone number to a HTTPS URL to request an authentication code,
• the phone receives an authentication code in the text message,
• the authentication code is used, again over HTTPS, to obtain a password.

These passwords are quite long and never visible to the user, making them hard to steal from a phone.

Authentication Overview

With the password, the client can log in to the not-really-XMPP server that WhatsApp uses. For this it uses the custom SASL mechanism WAUTH-1. To log in with the phone number XXXXXXXXXXXX, the following happens (I’m showing the XML representation of the protocol, this is not what is actually sent):

• The client sends:

  <auth xmlns="urn:ietf:params:xml:ns:xmpp-sasl" user="XXXXXXXXXXXX" mechanism="WAUTH-1" />

  
  
• The server responds with a some challenge (here YYYYYYYYYYYYYYYYYYYY):

  <challenge xmlns="urn:ietf:params:xml:ns:xmpp-sasl">YYYYYYYYYYYYYYYYYYYY</challenge>

  
  
• To respond to the challenge, the client generates a key using PBKDF2 with the user’s password, the challenge data as the salt and SHA1 as the hash function. It only uses 16 iterations of PBKDF2, which is a little low these days, but we know the password is quite long and random so this does not concern me greatly. 20 bytes from the PBKDF2 result are used as a key for RC4, which is used to encrypt and MAC XXXXXXXXXXXX || YYYYYYYYYYYYYYYYYYYY || UNIX timestamp:

  <response xmlns="urn:ietf:params:xml:ns:xmpp-sasl">ZZZZZZZZZZZZZ</response>

  
  
• From now on, every message is encrypted and MACed (using HMAC-SHA1) using this key.

Mistake #1: The same encryption key in both directions

Lets recall how RC4 is supposed to work: RC4 is a PRNG that generates a stream of bytes, which are xored with the plaintext that is to be encrypted. By xoring the ciphertext with the same stream, the plaintext is recovered.
However, recall that:

(A ^ X) ^ (B ^ X) = A ^ B

In other words: if we have two messages encrypted with the same RC4 key, we can cancel the key stream out!
As WhatsApp uses the same key for the incoming and the outgoing RC4 stream, we know that ciphertext byte i on the incoming stream xored with ciphertext byte i on the outgoing stream will be equal to xoring plaintext byte i on the incoming stream with plaintext byte i of the outgoing stream. By xoring this with either of the plaintext bytes, we can uncover the other byte.
This does not directly reveal all bytes, but in many cases it will work: the first couple of messages exchanged are easy to predict from the information that is sent in plain. All messages still have a common structure, despite the binary encoding: for example, every stanza starts with 0xf8. Even if a byte is not known fully, sometimes it can be known that it must be alphanumeric or an integer in a specific range, which can give some information about the other byte.

Mistake #2: The same HMAC key in both directions

The purpose of a MAC is to authenticate messages. But a MAC by itself is not enough to detect all forms of tampering: an attacker could drop specific messages, swap them or even transmit them back to the sender. TLS counters this by including a sequence number in the plaintext of every message and by using a different key for the HMAC for messages from the server to the client and for messages from the client to the server. WhatsApp does not use such a sequence counter and it reuses the key used for RC4 for the HMAC.
When an attacker retransmits, swaps or drops messages the receiver can not notice that, except for the fact that the decryption of the message is unlikely to be a valid binary-XMPP message. However, by transmitting a message back to the sender at exactly the same place in the RC4 stream as it was originally transmitted will make it decrypt properly.  :)

Adobe has just disclosed that one of their servers has been hacked

While their investigations are still ongoing, Adobe has shared a few details on what they believe could have been accessed and obtained in the hack — and it’s a big one.

From what Adobe has shared so far, it sounds like the hackers had access to encrypted data for as many as 2.9 million customers. While Adobe stresses that the data is encrypted and that they “do not believe the attackers removed decrypted credit or debit card numbers”, that data — encrypted or not — is definitely notsomething they want out in the wild.

Adobe has yet to disclose how that data was encrypted, so it’s currently unclear just how secure it is.

Meanwhile, it also appears that the hackers may have been able to access the source code for at least three of Adobe’s products: Acrobat, ColdFusion, and ColdFusion Builder. This goes hand in hand with a report from Brian Krebs this morning, who noted that he and a fellow researcher had discovered at least 40GB of Adobe source code available on a hacking group’s private server.

Beyond the obvious business implications of having your otherwise locked down source code floating around in the wild, there are potentially massive security concerns here. Once you’ve got the source code for an application in hand, it becomes much easier to dig up the stealthy lil’ security screw ups that might otherwise go unnoticed. Combine this new potential for big zero-day exploits with the many,many millions of Adobe Acrobat (Adobe’s official PDF reader) installs around the world, and this all starts to get pretty worrisome.

Exclusive : New Touch ID hack allows hacker to unlock an iPhone by multiple fingerprints

The Iranian group defeated the very basic phenomenon of an iPhone Fingerprinting scanner, which allows them to unlock an iPhone device with multiple Fingerprints.

                                           

Apple‘s iPhone 5s, was launched just available in stores two weeks before with a new feature of biometrics-based security system called "Touch ID", that involves analyzing a user’s fingerprint and using that to unlock the phone.

Apple launched the technology that it promises will better protect devices from criminals and snoopers seeking access. With this you can purchase things from the iTunes App Store. Basically, you can now use it in place of your password.

"Fingerprint is one of the best passcodes in the world. It's always with you, and no two are exactly alike," according to the Apple's website.

Last week Germany Hackers showed that how they were able to deceive Apple’s latest security feature into believing they’re someone they’re not, using a well-honed technique for creating a latex copy of someone's fingerprint. Another interesting fact is that, Touch ID is not only designed to scan the fingerprints of your fingers, it works with various human body parts and appendages which are also not fingers.

An Iranian group of iPhone Geeks from Tehran running a blog i.e. "i-Phone.ir" contacted 'The Hacker News' with another awesome Touch ID hack, shown that how they defeated the very basic phenomenon of Fingerprinting scanner i.e. "No two Fingerprints are exactly alike".

According to Apple, the chance that Touch ID will misread a finger is 1 in 50,000 , this is because Touch ID is not designed to capture the fingerprint in strict mode. It scans the fingerprint on a very high-resolution (2400 dpi), to get and match the partial parts of an impression for faster unlocking.

If the iPhone is not able to scan the thumb impression in the strict mode to be unique, there is a possibility that out of 1000 thumb impressions iPhone's Touch ID system can count 2-3 impressions as of the same person.

It could be a feature only if 5 different keys (fingers) are of the same person, but here we have 5 different people with the same key (finger), absolutely Touch ID is not a family key system that should work for Dad-Mom-sister and elder brother. it worked successfully for both and many times on latest IOS firmware 7.0.2 and iPhone users will not receive any patch soon for this.

How to install Android Emulator on Windows 7

As part of my testing work, I am currently working on using webdriver to test on Android. So I had to install Android Emulator on Windows 7. Below are the sequential steps and I hope it will ease some pain on getting Android emulator on your Windows 7 box.

Download the installer from http://developer.android.com/sdk/index.html

1. Install it to a location (like: C:\Program Files\Android)
2. Launch “SDK Manager.exe”
3. It will launch a “Android SDK and AVD Manager”. By default “Installed packages” will be highlighted. On the pop up “Choose Packages to Install”, there will be some packages selected already. Go ahead with the “Install”.

4.    Once it is done, select “Virtual Devices” to create one for you. Click on “New” and enter some name. Target as “Android 2.2 – API Level 8”. Select Size as “512” and “Built-in” to be “WVGA854” and click on “Create AVD”.

5. Once done select the Virtual device you created and click on Start. You can find the “Start” button on the right panel in the above shown image. Clicking “Start” will launch another pop-up, just say “Launch” and proceed.

How To Remove Google Ads From Android Apps - Lucky Patcher

Hello guys, Today I have an Android video tutorial for you! We all hate Ads on apps, they're disturbing, and we don't really want to pay just to remove them.. So today I will show you how to remove them from your apps For this tutorial you need: 

1. A Rooted Android Device 
2. Lucky Patcher (Download HERE) 
3. An App With Google Ads

Video tutorial : https://vimeo.com/65024892

How To Run Tor Browser As Root In Linux

Hello guys, today I'm going to show you how to run Tor browser as root in linux (backtrack in the video), I made this video because many people were asking how to get a VPN on backtrack, because most of them doesn't work, so here is a Tutorial on how to make Tor work in backtrack :)

Video tutorial : http://vimeo.com/46954765