File scan report
Verdict Malicious
Is info. exe safe? No, we rate this exact file malicious.
Unsigned executable flagged by 19 engines including two major as abltrojan with data-destruction behavior.
Strong evidence · Two or more major antivirus engines agree.
Treat as malicious; remove the file and scan the system for related artifacts.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
19 of 71 flagged
- Flagged 19
- No detection 52
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The file info.exe shows clear malicious signals from multiple engines and an offensive MITRE technique. Two major detections plus consistent trojan labeling across 19 engines support a malicious verdict despite weak family consensus and clean sandbox outcome.
Nineteen engines report malicious, two of which are major, with labels converging on abltrojan variants. The presence of in offensive techniques indicates destructive capability typical of trojans. The binary is unsigned and carries a medium-prevalence threat label that matches the engine families. Absence of sandbox malice and low major agreement are noted but insufficient to override the volume and tier of detections.
What We Detected
19 antivirus engines flagged the sample, including Fortinet and Trend Micro at major. Labels reference abltrojan, ABlTrojan, and generic trojan families. One sandbox recorded T1485 data-destruction behavior.
Threat Behavior
The executable writes multiple temporary DLLs and exhibits debug-environment detection. No malicious files it created or external host contacts were observed, yet the offensive MITRE technique and engine consensus indicate trojan functionality.
What To Do Now
Quarantine or delete the file. Avoid execution on production systems. Submit the hash to threat-intel platforms for further correlation.
Where this verdict could be wrong1 caveat
- tier1FamilyConsensus.strong=false (only 1 engine) and hasMaliciousSandboxVerdict=false could indicate borderline rule-based noise, but 19 detections including major override this.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No malicious files it created
- No contacted malicious hosts
- Medium prevalence with 29 submitters
- Unsigned PE with 19 malicious detections
- Offensive present
- Consistent abltrojan family labels across engines
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 12sandbox rule tags
- 3spawned processes
- 0network contacts
- 30filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
info.exe
9f4a974810932b8dfc8a80417b3323054cbe4e90cc6885715b2467370bfd2733
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
info.exe
"C:\Users\<USER>\Desktop\info.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
info.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
VCRUNTIME140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\VCRUNTIME140.dll
Test run - Evidence 5 of 5: Written fileSeen in the test run
_bz2.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_bz2.pyd
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
12MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1059· Runs commands
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1485
- T1497.001· Sandbox evasion
- T1518.001· Checks your AV
- T1574.002· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
info.exe"C:\Users\<USER>\Desktop\info.exe"info.exeinfo.exe"C:\Users\user\Desktop\info.exe"
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\VCRUNTIME140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_bz2.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_ctypes.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_decimal.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_hashlib.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_lzma.pyd
Show all 30 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\_socket.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-console-l1-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-datetime-l1-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-debug-l1-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-errorhandling-l1-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l1-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l1-2-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l2-1-0.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-handle-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-console-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-datetime-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-debug-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-errorhandling-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l1-2-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-file-l2-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-handle-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-heap-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-interlocked-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-libraryloader-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-localization-l1-2-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-memory-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-namedpipe-l1-1-0.dll - Deleted
C:\Users\<USER>\AppData\Local\Temp\_MEI58562\api-ms-win-core-processenvironment-l1-1-0.dll
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 10 have no saved verdict and were not checked; that is missing coverage, not a finding.
- d045a72c3e4d21165e93…a310e8Not checkedno saved verdict
- eb8fe2778c54213aa2cc…588e74Not checkedno saved verdict
- 6f50b4dc2129ff8e2280…5de06cNot checkedno saved verdict
- 8eccaba9321df69182ee…7395aeNot checkedno saved verdict
- 5783c5c5a3ffce181691…7cfcc5Not checkedno saved verdict
- 39e363c47d4d45beda15…76453cNot checkedno saved verdict
- 91d7a4c39baac78c595f…dcd42cNot checkedno saved verdict
- 6e6bfdc656f0cf22fabb…e57ab2Not checkedno saved verdict
- b545db2339ae74c52336…619b68Not checkedno saved verdict
- b9ae70e8f74615ea2dc6…3424f2Not checkedno saved verdict
Chapter 04
Technical details
19 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 19
- Fortinet (major engine)W32/PossibleThreat
- TrellixENS (major engine)Artemis!B049A74577D2
- TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101DH26ZK
- CrowdStrikewin/malicious_confidence_60% (W)
- CTXexe.trojan.generic
- CylanceUnsafe
- CynetMalicious (score: 100)
- DeepInstinctMALICIOUS
File fingerprint
- Last analyzed
- May 30, 2026, 6:52 PM UTC
- SHA-256
9f4a974810932b8dfc8a80417b3323054cbe4e90cc6885715b2467370bfd2733- SHA-1
09d45b4e9be02dfa05dfc60b919f290e88898723- MD5
b049a74577d29889cd1db21c80da6761
About this file
info.exe is a Win32 EXE file of 6.3 MB.
- Type and size
- Win32 EXE · 6.3 MB
- Signer
- UnsignedNo code signature.
- First seen
- Apr 19, 2025On VirusTotal.
- Submitted by
- 29 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Antivirus consensus
19 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
The 19 detections come from 17 independent scan engines: several vendors license the same engine, so their results are one vote.
- Tier-118 engines3flagged
- Tier-236 engines11flagged
- Low-trust17 engines5flagged
View all 75 engine results
- CrowdStrikeMalicious: win/malicious_confidence_60% (W)
- CTXMalicious: exe.trojan.generic
- CylanceMalicious: Unsafe
- CynetMalicious: Malicious (score: 100)
- DeepInstinctMalicious: MALICIOUS
- ElasticMalicious: malicious (moderate confidence)
- FortinetMalicious: W32/PossibleThreat
- GoogleMalicious: Detected
- GridinsoftMalicious: Trojan.Win64.Downloader.cl
- JiangminMalicious: TrojanSpy.Agent.afwu
- LionicMalicious: Trojan.Win64.Shelm.tsCg
- McAfeeDMalicious: ti!9F4A97481093
- PaloaltoMalicious: generic.ml
- SangforMalicious: Trojan.Win32.Save.a
- SentinelOneMalicious: Static AI - Suspicious PE
- SkyhighMalicious: BehavesLike.Win64.Dropper.vc
- TrellixENSMalicious: Artemis!B049A74577D2
- TrendMicro-HouseCallMalicious: Trojan.Win64.Gen.TL0101DH26ZK
- VaristMalicious: W64/ABlTrojan.HZJM-7547
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- DrWebClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- GDataClean
- huorongClean
- IkarusClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- MalwarebytesClean
- MaxSecureClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- RisingClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrendMicroClean
- TrustlookNo result
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is info.exe malware?
What is info.exe?
How many antivirus engines detected info.exe?
I already downloaded and ran info.exe — what should I do?
How do I remove info.exe?
What kind of malware is info.exe?
What is the SHA-256 hash of info.exe?
How up to date is this analysis of info.exe?
Community
Member reviews and reports for this exact file hash.