Spectating the Win32/Filecoder.OLQ detection name means that your computer is in big danger. This computer virus can correctly be identified as ransomware – sort of malware which encrypts your files and asks you to pay for their decryption. Removing it requires some specific steps that must be taken as soon as possible.
Win32/Filecoder.OLQ detection is a virus detection you can spectate in your computer. It generally appears after the provoking activities on your PC – opening the suspicious e-mail, clicking the advertisement in the Internet or installing the program from unreliable resources. From the second it appears, you have a short time to do something about it until it begins its malicious action. And be sure – it is much better not to wait for these destructive things.
What is Win32/Filecoder.OLQ virus?
Win32/Filecoder.OLQ Summary
In summary, Win32/Filecoder.OLQ malware activities in the infected computer are next:
- Yara rule detections observed from a process memory dump/dropped files/CAPE;
- NtSetInformationThread: attempt to hide thread from debugger;
- Creates RWX memory;
- Attempts to connect to a dead IP:Port (255 unique times);
- Dynamic (imported) function loading detected;
- Manipulates data from or to the Recycle Bin;
- Authenticode signature is invalid;
- Writes a potential ransom message to disk;
- Creates or sets a registry key to a long series of bytes, possibly to store a binary or malware config;
- Exhibits possible ransomware file modification behavior;
- CAPE detected the Conti malware family;
- Collects information to fingerprint the system;
- Ciphering the documents located on the victim’s drives — so the victim cannot check these files;
- Blocking the launching of .exe files of anti-virus programs
- Blocking the launching of installation files of security tools
Ransomware has been a nightmare for the last 4 years. It is challenging to imagine a more dangerous malware for both individuals and businesses. The algorithms utilized in Win32/Filecoder.OLQ (usually, RHA-1028 or AES-256) are not hackable – with minor exclusions. To hack it with a brute force, you need to have a lot more time than our galaxy already exists, and possibly will exist. But that virus does not do all these unpleasant things without delay – it can require up to a few hours to cipher all of your files. Hence, seeing the Win32/Filecoder.OLQ detection is a clear signal that you need to begin the clearing procedure.
Where did I get the Win32/Filecoder.OLQ?
Ordinary tactics of Win32/Filecoder.OLQ distribution are common for all other ransomware variants. Those are one-day landing sites where victims are offered to download and install the free software, so-called bait e-mails and hacktools. Bait emails are a pretty modern method in malware spreading – you get the email that imitates some standard notifications about shipments or bank service conditions changes. Within the email, there is a malicious MS Office file, or a link which opens the exploit landing site.

Malicious email message. This one tricks you to open the phishing website.
Avoiding it looks fairly simple, however, still needs tons of awareness. Malware can hide in different places, and it is much better to stop it even before it goes into your system than to depend on an anti-malware program. Basic cybersecurity awareness is just an important thing in the modern world, even if your relationship with a computer stays on YouTube videos. That can keep you a lot of money and time which you would certainly spend while looking for a solution.
Win32/Filecoder.OLQ malware technical details
File Info:
name: A2123B6A0489862004A8.mlwpath: /opt/CAPEv2/storage/binaries/06ad123df8f3fcc6ca4785c0b52fc57e6e54f44e403fca2fdbd339580d3c53b0crc32: 09EB6878md5: a2123b6a0489862004a8ea41e6528e89sha1: fb5fb8cf0e779fe9e353df0bb9fd61f492845516sha256: 06ad123df8f3fcc6ca4785c0b52fc57e6e54f44e403fca2fdbd339580d3c53b0sha512: 74f73be199372ef211bc1a79e199723aba49ff05ed09088b9ab2f1f1887c147f859ca8ce6af71431e298e2b44e37219b524c9ef2256c6989dfd5ef467ab28784ssdeep: 1536:V+5ZpiURRRUr2oOsDGrbH+TY/59dNiD3WyJjuzyXrx+j6cmh7:VWpiURfUr2oOsDGrz+TY6D3Wy0yl+jY7type: PE32 executable (GUI) Intel 80386, for MS Windowstlsh: T13963C44A7609EB30F18794B696FD2A57699E9938835F85C3EBD0C09A7561CC7B830F03sha3_384: d1c51c776230ae254e6bdd38883b6662bade34830ab1c8b2e1befe9b067356744d28c8b826c1edff69f5952f882452f9ep_bytes: e89bfeffff33c0c21000cccccccccccctimestamp: 1984-02-21 20:01:52Version Info:
0: [No Data]
Win32/Filecoder.OLQ also known as:
| Bkav | W32.AIDetect.malware2 |
| MicroWorld-eScan | Gen:Variant.Lazy.202657 |
| ALYac | Gen:Variant.Lazy.202657 |
| Cylance | Unsafe |
| Cybereason | malicious.a04898 |
| Cyren | W32/Agent.CC.gen!Eldorado |
| Symantec | Ransom.Conti!gm1 |
| Elastic | Windows.Ransomware.Conti |
| ESET-NOD32 | a variant of Win32/Filecoder.OLQ |
| APEX | Malicious |
| Paloalto | generic.ml |
| Kaspersky | VHO:Trojan-Ransom.Win32.GenericCryptor.gen |
| BitDefender | Gen:Variant.Lazy.202657 |
| Ad-Aware | Gen:Variant.Lazy.202657 |
| F-Secure | Trojan.TR/Crypt.XPACK.Gen |
| DrWeb | Trojan.Encoder.35508 |
| VIPRE | Gen:Variant.Lazy.202657 |
| TrendMicro | Ransom_Conti.R06CC0DGS22 |
| Trapmine | malicious.high.ml.score |
| FireEye | Generic.mg.a2123b6a04898620 |
| SentinelOne | Static AI – Malicious PE |
| GData | Gen:Variant.Lazy.202657 |
| Avira | TR/Crypt.XPACK.Gen |
| Arcabit | Trojan.Lazy.D317A1 |
| ZoneAlarm | VHO:Trojan-Ransom.Win32.GenericCryptor.gen |
| Microsoft | Ransom:Win32/Conti.AD!MTB |
| Cynet | Malicious (score: 100) |
| AhnLab-V3 | Ransomware/Win.Conti.C5216362 |
| MAX | malware (ai score=81) |
| VBA32 | BScope.TrojanRansom.Conti |
| TrendMicro-HouseCall | Ransom_Conti.R06CC0DGS22 |
| Rising | Ransom.Conti!1.DF1E (CLASSIC) |
| Ikarus | Trojan-Ransom.BlueSky |
| MaxSecure | Trojan.Malware.300983.susgen |
| Fortinet | W32/Filecoder.OLQ!tr.ransom |
| BitDefenderTheta | AI:Packer.6CBF18991E |
| CrowdStrike | win/malicious_confidence_100% (D) |
Leave a Comment