What to verify before removal
Use this report for a controlled check of Should I remove “Worm.Win32.VBNA.aitt”? when the affected machine shows suspicious processes, dropped files, or payload delivery behavior. The goal is to verify the exact file and persistence path before quarantine.
Start by comparing the local file name with 31A035192F5C47C84DDA.mlw, then review the behavior notes for persistence entries, dropped files, unusual processes, and browser or network changes. This helps separate a matching detection from a different file that only shares a similar alert name.
- Observed file
- 31A035192F5C47C84DDA.mlw
- Compare the suspicious file name with 31A035192F5C47C84DDA.mlw.
- Confirm the detection name matches Should I remove “Worm.Win32.VBNA.aitt”? before removing related files.
- Review the report for persistence entries, dropped files, unusual processes, and browser or network changes so the cleanup is based on observed behavior, not only the label.
- Run a full scan, quarantine confirmed detections, and restart before signing back in to sensitive accounts.
The Worm.Win32.VBNA.aitt is considered dangerous by lots of security experts. When this infection is active, you may notice unwanted processes in Task Manager list. In this case, it is adviced to scan your computer with GridinSoft Anti-Malware.
What Worm.Win32.VBNA.aitt virus can do?
- Behavioural detection: Executable code extraction – unpacking
- Reads data out of its own binary image
- CAPE extracted potentially suspicious content
- Drops a binary and executes it
- Authenticode signature is invalid
- Behavioural detection: Injection (inter-process)
- CAPE detected the embedded pe malware family
- Anomalous binary characteristics
- Attempts to modify Explorer settings to prevent hidden files from being displayed
- Yara detections observed in process dumps, payloads or dropped files
How to determine Worm.Win32.VBNA.aitt?
File Info:
name: 31A035192F5C47C84DDA.mlwpath: /opt/CAPEv2/storage/binaries/08efe5716b1f32e5ca0fbe87baf74a334265049e1f2824b3c07ccf95cf72d4fecrc32: AA630108md5: 31a035192f5c47c84dda7856e992bf8fsha1: 91f2b3dc2415308805a7b56b648f60d04e633b37sha256: 08efe5716b1f32e5ca0fbe87baf74a334265049e1f2824b3c07ccf95cf72d4fesha512: 08f5b47a5c15e8121068c79fd3f161ebe88a9e983914c9c74e4230bb4d9929a0f6a93599390a006a665c5cf47ec9822d776ed6024dfc279956669f740e9ebfadssdeep: 1536:3yPgSNEY1ObCYUXhXAXzXakcUckn98kMEW7G:UVG0kcUckn98kME9type: PE32 executable (GUI) Intel 80386, for MS Windowstlsh: T1A8436F6EFE05144BD60D6A313E67CADF1EB764CE2E4F1A87251873789D36E103825A0Bsha3_384: 68cb13902ea9d86043e54dff92aa54b8f13cdb8e7d322e17c8b706663526f23b0fe9048307bae8d33404cd28fed216b7ep_bytes: 6874124000e8eeffffff000040000000timestamp: 2010-07-08 11:37:18Version Info:
Translation: 0x0409 0x04b0ProductName: uFileVersion: 6.96ProductVersion: 6.96InternalName: uuGBHNxzOriginalFilename: uuGBHNxz.exe
Worm.Win32.VBNA.aitt also known as:
| Bkav | W32.AIDetectMalware |
| Lionic | Worm.Win32.VBNA.lmeS |
| MicroWorld-eScan | Gen:Variant.Midie.59905 |
| ClamAV | Win.Trojan.VB-1146 |
| FireEye | Generic.mg.31a035192f5c47c8 |
| CAT-QuickHeal | Worm.VBNA.gen |
| Skyhigh | BehavesLike.Win32.VBObfus.qm |
| ALYac | Gen:Variant.Midie.59905 |
| Cylance | unsafe |
| Sangfor | Suspicious.Win32.Save.a |
| K7AntiVirus | Trojan ( f1000d011 ) |
| Alibaba | Worm:Win32/Vobfus.441ce089 |
| K7GW | Trojan ( f1000d011 ) |
| Cybereason | malicious.c24153 |
| BitDefenderTheta | AI:Packer.3BEB779A20 |
| VirIT | Worm.Win32.VB.12.O |
| Symantec | W32.Changeup |
| Elastic | malicious (high confidence) |
| ESET-NOD32 | Win32/AutoRun.VB.RD |
| APEX | Malicious |
| Cynet | Malicious (score: 100) |
| Kaspersky | Worm.Win32.VBNA.aitt |
| BitDefender | Gen:Variant.Midie.59905 |
| NANO-Antivirus | Trojan.Win32.Inject.covlpb |
| Avast | Win32:VB-PQX [Wrm] |
| Tencent | Worm.Win32.VBNA.hew |
| Emsisoft | Gen:Variant.Midie.59905 (B) |
| Baidu | Win32.Worm.VB.as |
| F-Secure | Worm:W32/Vobfus.AX |
| DrWeb | Trojan.Inject.8955 |
| VIPRE | Gen:Variant.Midie.59905 |
| TrendMicro | WORM_ESFURY.SMA |
| Trapmine | suspicious.low.ml.score |
| Sophos | W32/Autorun-BFG |
| Ikarus | Worm.Win32.Vobfus |
| GData | Gen:Variant.Midie.59905 |
| Jiangmin | Worm.VBNA.bjbf |
| Webroot | W32.Obfuscated.Gen |
| Detected | |
| Avira | TR/Dldr.Gaat.A |
| Antiy-AVL | Worm/Win32.WBNA.gen |
| Kingsoft | malware.kb.a.1000 |
| Xcitium | TrojWare.Win32.VB.SWA@527lh3 |
| Arcabit | Trojan.Midie.DEA01 |
| ZoneAlarm | Worm.Win32.VBNA.aitt |
| Microsoft | Worm:Win32/Vobfus.R |
| Varist | W32/VB.BA.gen!Eldorado |
| AhnLab-V3 | Win32/Vbna4.worm.Gen |
| McAfee | Downloader-CJX.c |
| VBA32 | Worm.VBNA |
| Malwarebytes | Generic.Malware.AI.DDS |
| Panda | W32/Vobfus.EQ |
| TrendMicro-HouseCall | WORM_ESFURY.SMA |
| Rising | Worm.VobfusEx!1.99EB (CLASSIC) |
| SentinelOne | Static AI – Malicious PE |
| Fortinet | W32/Injector.ADYA!tr |
| AVG | Win32:VB-PQX [Wrm] |
| DeepInstinct | MALICIOUS |
| CrowdStrike | win/malicious_confidence_100% (W) |
How to remove Worm.Win32.VBNA.aitt?
Verify the infection before changing system settings
Use GridinSoft Anti-Malware to run a full scan, review detected persistence entries, and quarantine confirmed threats before restarting Windows.
- Download and install GridinSoft Anti-Malware.
- Open GridinSoft Anti-Malware and perform a “Standard scan“.
- “Move to quarantine” all items.
- Open “Tools” tab – Press “Reset Browser Settings“.
- Select proper browser and options – Click “Reset”.
- Restart your computer.