Seeing the Trojan.BundleInstaller detection name means that your computer is in big danger. This computer virus can correctly be named as ransomware – virus which encrypts your files and asks you to pay for their decryption. Deleteing it requires some unusual steps that must be taken as soon as possible.
Trojan.BundleInstaller detection is a virus detection you can spectate in your system. It frequently shows up after the provoking actions on your PC – opening the dubious email, clicking the advertisement in the Web or installing the program from dubious resources. From the instance it appears, you have a short time to do something about it before it starts its harmful activity. And be sure – it is much better not to await these harmful effects.
What is Trojan.BundleInstaller virus?
Trojan.BundleInstaller is ransomware-type malware. It looks for the documents on your disk, encrypts it, and after that asks you to pay the ransom for getting the decryption key. Besides making your files inaccessible, this virus also does a ton of damage to your system. It modifies the networking settings in order to stop you from checking out the removal tutorials or downloading the anti-malware program. In rare cases, Trojan.BundleInstaller can additionally stop the launching of anti-malware programs.
Trojan.BundleInstaller Summary
In summary, Trojan.BundleInstaller malware actions in the infected computer are next:
- SetUnhandledExceptionFilter detected (possible anti-debug);
- Yara rule detections observed from a process memory dump/dropped files/CAPE;
- Guard pages use detected – possible anti-debugging.;
- Dynamic (imported) function loading detected;
- Performs HTTP requests potentially not found in PCAP.;
- HTTPS urls from behavior.;
- Unconventionial language used in binary resources: Greek;
- Authenticode signature is invalid;
- Sniffs keystrokes;
- Creates or sets a registry key to a long series of bytes, possibly to store a binary or malware config;
- Network activity contains more than one unique useragent.;
- Attempts to modify proxy settings;
- Encrypting the documents located on the victim’s disk — so the victim cannot check these documents;
- Blocking the launching of .exe files of anti-malware programs
- Blocking the launching of installation files of security tools
Ransomware has been a horror story for the last 4 years. It is hard to realize a more dangerous virus for both individuals and companies. The algorithms used in Trojan.BundleInstaller (typically, RHA-1028 or AES-256) are not hackable – with minor exclusions. To hack it with a brute force, you need to have more time than our galaxy actually exists, and possibly will exist. But that virus does not do all these bad things instantly – it can require up to several hours to cipher all of your documents. Therefore, seeing the Trojan.BundleInstaller detection is a clear signal that you have to begin the elimination procedure.
Where did I get the Trojan.BundleInstaller?
Common methods of Trojan.BundleInstaller injection are usual for all other ransomware variants. Those are one-day landing websites where users are offered to download the free app, so-called bait emails and hacktools. Bait emails are a pretty new method in malware distribution – you receive the email that mimics some normal notifications about shippings or bank service conditions changes. Inside of the e-mail, there is a corrupted MS Office file, or a web link which leads to the exploit landing page.

Malicious email message. This one tricks you to open the phishing website.
Preventing it looks quite easy, however, still demands tons of recognition. Malware can hide in various places, and it is much better to prevent it even before it goes into your PC than to depend on an anti-malware program. Simple cybersecurity awareness is just an essential item in the modern-day world, even if your relationship with a PC stays on YouTube videos. That can save you a lot of time and money which you would spend while searching for a fix guide.
Trojan.BundleInstaller malware technical details
File Info:
name: 1D80FC3AAB027CFEA186.mlwpath: /opt/CAPEv2/storage/binaries/067c2a6acec36be5445ceb58ea1a68bb81f8cb8c62725b32dd6f857eaaf33ac8crc32: 4629F0BEmd5: 1d80fc3aab027cfea186d11999b22992sha1: 8585fca639005d63038243842e760745e0262257sha256: 067c2a6acec36be5445ceb58ea1a68bb81f8cb8c62725b32dd6f857eaaf33ac8sha512: 675cd4b512f15bea9841de6116204a334416e28c975523dc873e0e17086fb63a2e4884a6c11b06bedd3fd12bea839f12a05a160d624c1021257da25332ec062essdeep: 98304:jDIBn68FVdPQ7hx66pX4HkWBjHegtSYN4GECVkNFiFSFa:IDypq7zSYN4gkNFiFSFtype: PE32 executable (GUI) Intel 80386, for MS Windowstlsh: T1A7266C2A39CA98B6C5A0D63F0134E139C3768553EAEB5A6712994F0735E3B603ECF345sha3_384: 0efc4cd7e220454c78871e397ef6931088fd190f835c5e41e610df91f6544c428c7c19f007a0568e91fd4d9465e42752ep_bytes: e88b800000e989feffff3b0dc0bc5800timestamp: 2011-04-15 11:00:07Version Info:
CompanyName: ZodiarkFileDescription: Lineage II LauncherFileVersion: 1.0.0.1InternalName: L2Updater.exeLegalCopyright: © 2010 Zodiark. All rights reserved.OriginalFilename: L2Updater.exeProductName: Lineage II LauncherProductVersion: 1.0.0.1Translation: 0x0409 0x04b0
Trojan.BundleInstaller also known as:
| Lionic | Trojan.Win32.Atom.tqHT |
| MicroWorld-eScan | Trojan.GenericKD.38224082 |
| FireEye | Trojan.GenericKD.38224082 |
| McAfee | Artemis!1D80FC3AAB02 |
| Cylance | Unsafe |
| Sangfor | Riskware.Win32.Uwamson.A |
| APEX | Malicious |
| Paloalto | generic.ml |
| BitDefender | Trojan.GenericKD.38224082 |
| NANO-Antivirus | Trojan.Win32.Atom.fzjxmm |
| Ad-Aware | Trojan.GenericKD.38224082 |
| McAfee-GW-Edition | BehavesLike.Win32.Dropper.rh |
| Emsisoft | Trojan.GenericKD.38224082 (B) |
| Ikarus | Trojan.Atom |
| GData | Trojan.GenericKD.38224082 |
| Jiangmin | Trojan.Atom.gv |
| MAX | malware (ai score=84) |
| Antiy-AVL | Trojan/Generic.ASMalwS.29C4CBE |
| Microsoft | Trojan:Win32/Wacatac.B!ml |
| ALYac | Trojan.GenericKD.38224082 |
| VBA32 | TrojanRansom.Atom |
| Malwarebytes | Trojan.BundleInstaller |
| TrendMicro-HouseCall | TROJ_GEN.R002H09LB21 |
| Yandex | Trojan.GenAsa!XeUQvO+X6nE |
| Fortinet | W32/PossibleThreat |
Leave a Comment