• This malware was used in the EvilGrab campaign, which targets victims in Japan and China.This backdoor arrives on a system as a file dropped by other malware or as a file downloaded unknowingly by users when visiting malicious sites.
    Read more   

  • This malware is involved in the targeted attacks that took advantage of an unpatched Microsoft Office vulnerability, namely CVE-2013-3906, on November 2013. Victims of this malware may find the security of their systems compromised.
    Read more   

  • This malware is involved in the targeted attacks that took advantage of an unpatched Microsoft Office vulnerability, namely CVE-2013-3906, on November 2013. Victims of this malware may find the security of their systems compromised.
    Read more   

  • This CryptoLocker is downloaded by a ZeuS/ZBOT variant detected as TSPY_ZBOT.VNA.
    Read more   

  • This malware is involved in a ZBOT spam campaign that targeted British users. Once the malicious attachment is opened, it inevitable leads to the download of ZBOT malware into the affected system.
    Read more   

  • This malware is involved in the CryptoLocker ransomware malicious spam campaign spotted on October 2013. It is the malicious attachment that, when executed, downloads more malware onto the affected system.
    Read more   

  • This malware makes use of “garbage” strings, which in actual hides the malicious code. The said malicious code is an obfuscated AutoIt script.
    Read more   

  • This malware is one of the latest ransomware variants known as cryptolockers. When executed, it encrypts files and displays a warning message informing users that even though the malware has been deleted on their system, the encrypted files are inaccessible.
    Read more   

  • This backdoor is a variant of the malware family BLYPT. It uses binary large objects (BLOB) to store information in the affected system's registry.
    Read more   

  • This backdoor is a variant of the malware family BLYPT. It uses binary large objects (BLOB) to store information in the affected system's registry.
    Read more