Hacking Team Hacked, Attackers Grab 400GB of Internal Data
Several readers sent word that notorious surveillance company Hacking Team has itself been hacked. Attackers made off with 400GB worth of emails, documents, and source code. The company is known for providing interception tools to government and law enforcement agencies. According to the leaked files, Hacking Team has customers in Egypt, South Korea, Kazakhstan, Saudi Arabia, Oman, Lebanon, Mongolia, Russia, Germany, Sudan, and the United States — to name a few. It has been labeled an enemy of the internet by Reporters Without Borders. "Clients have had their passwords exposed as well, as several documents related to contracts and configurations have been circulating online." Nobody knows yet who perpetrated the hack.
Someone started uploading all the HackingTeam source code to GitHub: https://github.com/hackedteam?...
There are also some signing keys for kernel drivers in here.
That's a bad day for Hacking Team and a good day for everyone else.
https://twitter.com/FredericJa...
Subject: UID=DE9J4B8GTF, CN=iPhone Distribution: HT srl, OU=DE9J4B8GTF, O=HT srl, C=IT
It's confirmed. One of the news stories (can't remember which one) said that HT would recommend that their clients purchase digital certs to sign the malware they bought in order to skirt anti-virus scans. Apparently most antivirus software will ignore legitamite looking signed apps with certs that have been timestamped. The GeoTrust cert is probably a test cert that HT uses.
Can someone please explain the significance and consequences of publishing this:
GeoTrust_SigningCertificateExported_2011.pfx
It's another couple good patters for antivirus software to look for and trigger upon finding.
Anyone infected with their rootkitted drivers four years ago and haven't had the malware update may find out about being infected with it.
If they used the same company name for their 2015 certificate as is used in the certs published, that would be another signature for AV software to trigger on if they kept your rootkitted drivers updated.
That's about it however.
The certificate is long expired so can't be used to sign any new code with.
You can also be pretty certain their next certificate (to be issued any day now, if not already) will be under a different name as well.