Pushdo Revolutions: Communication Encryption and Decoy Traffic
Recently, while researching a new bot (GoolBot), we found another Pushdo-like malware spreading with its help. After reversing, it became clear that it was a brand new evolution of the infamous multi-malware loader, for two essential reasons:
- While it used the 2nd generation Pushdo communication protocol (with minor varations), it encrypted its communications and routed them through the SSL port (443); while this encryption looked like SSL at first sight (which would be consistent with the choice of the port), it is actually NOT.
- There is a routine which generates some actual SSL traffic to a list of 339 known websites(legitimate, for the most part), obviously to drawn bot-to-C&C communication in a sea of decoys.
This latter point explains why so many webmasters are reporting that SSL traffic (coming from different IPs) is much higher than normal these days. The good news for them is that the additional traffic is not malicious (application-wise, that is), and the bad news is that an increase of actual viewers is not the cause of it: it’s just some dummy data generated by calls to the QueryPerformanceCounter API in the latest Pushdo evolution.
Memory snapshots (from a pushdo infected machine) below illustrate the former point about encryption:
After encryption (same memory space), just before sending:
Continue reading ‘Pushdo Revolutions: Communication Encryption and Decoy Traffic’ »