Seeing the Win32/Filecoder.GC detection usually means that your system is in big danger. This virus can correctly be identified as ransomware – sort of malware which encrypts your files and forces you to pay for their decryption. Deleteing it requires some unusual steps that must be taken as soon as possible.
Win32/Filecoder.GC detection is a malware detection you can spectate in your system. It often appears after the provoking actions on your computer – opening the suspicious email messages, clicking the advertisement in the Web or setting up the program from dubious sources. From the moment it shows up, you have a short time to do something about it before it begins its destructive action. And be sure – it is better not to await these destructive things.
What is Win32/Filecoder.GC virus?
Win32/Filecoder.GC Summary
In summary, Win32/Filecoder.GC malware activities in the infected system are next:
- SetUnhandledExceptionFilter detected (possible anti-debug);
- Yara rule detections observed from a process memory dump/dropped files/CAPE;
- Dynamic (imported) function loading detected;
- The binary likely contains encrypted or compressed data.;
- Authenticode signature is invalid;
- Steals private information from local Internet browsers;
- Exhibits possible ransomware file modification behavior;
- Attempts to disable or modify the Run command from the Start menu and the New Task (Run) command from Task Manager;
- Harvests cookies for information gathering;
- Ciphering the files kept on the victim’s disk drives — so the victim cannot use these files;
- Blocking the launching of .exe files of security tools
- Blocking the launching of installation files of security tools
Ransomware has actually been a horror story for the last 4 years. It is challenging to picture a more hazardous virus for both individuals and organizations. The algorithms used in Win32/Filecoder.GC (generally, RHA-1028 or AES-256) are not hackable – with minor exclusions. To hack it with a brute force, you need more time than our galaxy currently exists, and possibly will exist. However, that malware does not do all these bad things immediately – it may require up to a few hours to cipher all of your documents. Thus, seeing the Win32/Filecoder.GC detection is a clear signal that you should start the clearing process.
Where did I get the Win32/Filecoder.GC?
Ordinary tactics of Win32/Filecoder.GC spreading are standard for all other ransomware examples. Those are one-day landing websites where victims are offered to download and install the free software, so-called bait emails and hacktools. Bait emails are a relatively modern strategy in malware distribution – you receive the email that simulates some regular notifications about shipments or bank service conditions updates. Inside of the email, there is a malicious MS Office file, or a web link which opens the exploit landing site.

Malicious email message. This one tricks you to open the phishing website.
Avoiding it looks quite simple, however, still requires tons of attention. Malware can hide in various places, and it is far better to stop it even before it invades your PC than to trust in an anti-malware program. Simple cybersecurity awareness is just an important thing in the modern world, even if your relationship with a computer stays on YouTube videos. That can save you a great deal of time and money which you would spend while looking for a solution.
Win32/Filecoder.GC malware technical details
File Info:
name: 7A953D1D3F8B8F8266EC.mlwpath: /opt/CAPEv2/storage/binaries/478eee523fc5da711f40232d97edb50a5df7eb4d74049d7851f1d8d0f370a6b3crc32: F326710Fmd5: 7a953d1d3f8b8f8266ec28c01b0cb383sha1: 782988bc55741857d977dc34eb40f8c7b00e2c50sha256: 478eee523fc5da711f40232d97edb50a5df7eb4d74049d7851f1d8d0f370a6b3sha512: 33ae8303df34beeb132c96375704a37251d9384399fe71e5cc2abbe329ed1cd7a63159caa40a6c84b03fac394cd9bc1f0ff135e7887e5c84d5c01b2f5fb4421assdeep: 49152:YFRN3mducNCwZi3lQJikiKglmCPhtXA2BoZDgAm8VtBd:YFRN3VccBlQJikiKgwatX9type: PE32 executable (GUI) Intel 80386, for MS Windowstlsh: T1C3B5BF12FB42C5B2E8C201B56127AB7F5E39AE205728C9D3D7D12D798C311C26B3E799sha3_384: bd8e2772676dc1cb99248cfb5d5fdf35e22af2b9ce1ce072a10c99eab45c3b45048f26075abef7e8aed823c0e010cc47ep_bytes: e80f0a0000e97afeffff8b4df464890dtimestamp: 2022-06-07 15:04:13Version Info:
0: [No Data]
Win32/Filecoder.GC also known as:
| Bkav | W32.AIDetect.malware2 |
| Lionic | Trojan.Win32.Encoder.j!c |
| CAT-QuickHeal | Trojanransom.Encoder |
| McAfee | Artemis!7A953D1D3F8B |
| Cylance | Unsafe |
| Sangfor | Ransom.Win32.Encoder.gen |
| K7AntiVirus | Trojan ( 005940581 ) |
| Alibaba | Ransom:Win32/Encoder.3d79223a |
| K7GW | Trojan ( 005940581 ) |
| Cyren | W32/ABRisk.KPQV-1924 |
| Elastic | malicious (high confidence) |
| ESET-NOD32 | a variant of Win32/Filecoder.GC |
| APEX | Malicious |
| Paloalto | generic.ml |
| Cynet | Malicious (score: 100) |
| Kaspersky | HEUR:Trojan-Ransom.Win32.Encoder.gen |
| BitDefender | Gen:Variant.Lazy.193666 |
| MicroWorld-eScan | Gen:Variant.Lazy.193666 |
| Avast | Win32:Malware-gen |
| Tencent | Win32.Trojan.Filecoder.Ajvp |
| Ad-Aware | Gen:Variant.Lazy.193666 |
| Emsisoft | Gen:Variant.Lazy.193666 (B) |
| DrWeb | Trojan.Encoder.35446 |
| TrendMicro | Ransom_Encoder.R002C0WFC22 |
| McAfee-GW-Edition | BehavesLike.Win32.Generic.vh |
| FireEye | Gen:Variant.Lazy.193666 |
| Ikarus | Trojan-Ransom.FileCrypt |
| GData | Gen:Variant.Lazy.193666 |
| Jiangmin | Trojan.Encoder.aub |
| Webroot | W32.Malware.Gen |
| Avira | TR/FileCoder.toilc |
| Arcabit | Trojan.Lazy.D2F482 |
| ZoneAlarm | HEUR:Trojan-Ransom.Win32.Encoder.gen |
| Microsoft | Trojan:Win32/Wacatac.B!ml |
| AhnLab-V3 | Trojan/Win.Generic.C5159889 |
| ALYac | Trojan.Ransom.Filecoder |
| MAX | malware (ai score=86) |
| Malwarebytes | Ransom.Filecoder |
| TrendMicro-HouseCall | Ransom_Encoder.R002C0WFC22 |
| Rising | [email protected] (RDML:u4/Wd/Uyimx1ScKVIRBqyQ) |
| MaxSecure | Trojan.Malware.300983.susgen |
| Fortinet | W32/Filecoder.GC!tr |
| BitDefenderTheta | Gen:NN.ZexaF.34742.uwW@aGu1!Xhi |
| AVG | Win32:Malware-gen |
| Panda | Trj/RansomGen.A |
| CrowdStrike | win/malicious_confidence_100% (W) |
Leave a Comment