- Apr 13, 2013
- 3,224
People always look at horror when malware is signed- but should they? It is often mistaken that just because some software has a valid Digital Signature from a Vendor, that that Vendor is also Trusted. This (fortunately) is rarely the case. As an example:
Some may know that a strain of Python coded ransomware has showed up the past few weeks. The initial samples had a valid certificate from some jive-time company (La Crem LTD). The Blacklists quickly realized that not only was La Crem NOT on a TVL so would be treated like any other unknown file, but having that signature actually made their malware more easily detectable since after the initial detection La Crem was Blacklisted.
The point is this- any new variant with the now invalid certificate would be detected by everyone and their Mommy, whereas killing this certificate would make detection more problematic. And sure enough, a new variant was released (this one would only run the payload on reboot. And the cool thing is, just say you have a Document titled Important.doc; the ransomware will encrypt the original but will also create a file with the identical file name that would just present you with the Ransom Message. pretty Cool, no?).
Fun facts: The new variant is still less than 24 hours old. The initial detection results from VT was this: Antivirus scan for 2a42f2f98bffbdf3f354d162d4f707c33d9bb652cf45a3c8b358535b3c677198 at 2018-09-04 04:03:42 UTC - VirusTotal
Currently it is this (I renamed the file for my Zoo): Antivirus scan for 2a42f2f98bffbdf3f354d162d4f707c33d9bb652cf45a3c8b358535b3c677198 at 2018-09-04 14:01:15 UTC - VirusTotal
And I'm sure in 2 days everyone will detect this guy, and when the Pro AV Testings sites test various products against a few days after that everything will be Rainbows and Unicorns!
Some may know that a strain of Python coded ransomware has showed up the past few weeks. The initial samples had a valid certificate from some jive-time company (La Crem LTD). The Blacklists quickly realized that not only was La Crem NOT on a TVL so would be treated like any other unknown file, but having that signature actually made their malware more easily detectable since after the initial detection La Crem was Blacklisted.
The point is this- any new variant with the now invalid certificate would be detected by everyone and their Mommy, whereas killing this certificate would make detection more problematic. And sure enough, a new variant was released (this one would only run the payload on reboot. And the cool thing is, just say you have a Document titled Important.doc; the ransomware will encrypt the original but will also create a file with the identical file name that would just present you with the Ransom Message. pretty Cool, no?).
Fun facts: The new variant is still less than 24 hours old. The initial detection results from VT was this: Antivirus scan for 2a42f2f98bffbdf3f354d162d4f707c33d9bb652cf45a3c8b358535b3c677198 at 2018-09-04 04:03:42 UTC - VirusTotal
Currently it is this (I renamed the file for my Zoo): Antivirus scan for 2a42f2f98bffbdf3f354d162d4f707c33d9bb652cf45a3c8b358535b3c677198 at 2018-09-04 14:01:15 UTC - VirusTotal
And I'm sure in 2 days everyone will detect this guy, and when the Pro AV Testings sites test various products against a few days after that everything will be Rainbows and Unicorns!