Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Only 2 of the 69 antivirus engines that checked it flag this file, both less reliable ones, while 18 major antivirus engines report it clean. The combined sandbox verdict was clean and it is widely shared, first seen on Oct 18, 2025.
Both detections come from less reliable engines (APEX and Bkav), and none of the 18 major antivirus engines flag the file. The sandbox summary was clean, with no high-risk techniques corroborated by an artefact. The file was seen from 3420 submitters over about a year, and several dropped files are known-software reference entries. The dropped runtime libraries match a Python-packaged application. No malware family, malicious host contact or malicious dropped file turned up. The unsigned status and lack of publisher confirmation keep confidence moderate.
What we detected
Two of the 69 antivirus engines that checked it (APEX and Bkav) flagged the file with generic labels. Eighteen major antivirus engines, including Microsoft, Kaspersky, ESET and BitDefender, did not.Threat behavior
The combined sandbox verdict was clean across six runs. The program unpacks Python runtime libraries (image-handling modules and the Visual C++ runtime) into a temporary folder, which is normal for packaged Python apps. A file-encryption mapping appeared without any matching artefact and is not treated as evidence. The only network contact was a public DNS resolver, which is the analysis VM's own background traffic.What to do now
The evidence favours a false positive. As with any unsigned download, run it only if you trust where you got it, and keep your security software enabled.Where this verdict could be wrong3 caveats
- The file is unsigned and the only contact observed is a public DNS resolver; no publisher confirmation was found.
- Two engines (APEX, Bkav) flag it, and community annotations on the file are mixed, with some automated reports calling it suspicious or malicious.
- Similar files sharing the same import table include some judged malicious, though that table is typical of PyInstaller-built programs.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 18 major antivirus engines flag the file.
- The combined sandbox verdict was clean across six runs.
- It is widely shared: 3420 submitters over about a year.
- Five dropped files are known-software reference entries and none is malicious.
- The file is unsigned, so there is no publisher identity to verify.
- Two less reliable engines flag it with generic labels.
- Some similar files sharing the same import table were judged malicious, and community comments are mixed.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 6 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 6isolated sandbox runs
- 13sandbox rule tags
- 4spawned processes
- 0network contacts
- 16filesystem & mutex artifacts
Runtime behaviour
What this file did when executed
This file was detonated in 6 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANClean
Techniques observed in the sandbox
13MITRE 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
- T1057· Lists programs
- T1059· Runs commands
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1202
- T1486· File encryption
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
Observed activity
Processes started
4Programs the file ran, with their command lines.
file.exe"C:\Users\<USER>\Desktop\file.exe"cmd.exeC:\Windows\system32\cmd.exe /c "ver"IRUS_V6.7.5.exe"C:\Users\user\Desktop\IRUS_V6.7.5.exe"file.exe"C:\Users\user\Desktop\file.exe"
Files
15Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\MSVCP140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_avif.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_imaging.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_imagingcms.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_imagingft.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_imagingmath.cp314-win_amd64.pyd
Show all 15 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_imagingtk.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\PIL\_webp.cp314-win_amd64.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\VCRUNTIME140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\VCRUNTIME140_1.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\_asyncio.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\_bz2.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\_ctypes.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\_decimal.pyd - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI67802\_elementtree.pyd
Registry and auto-start
1Settings the file changed, including ways to start again after a restart.
- Set
HKEY_USERS\S-1-5-21-4270068108-2931534202-3907561125-1001\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.exe\OpenWithProgids\exefile
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
Local\SessionImmersiveColorMutex
Sandbox background — not the file
2The analysis machine's own processes and connections, recorded in every run.
- VM process
services.exeC:\Windows\system32\services.exe - VM host
dns.google
Dropped payload
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache. 5 have no saved verdict and were not checked; that is missing coverage, not a finding.
- 1d032e0c606b9b73ab66…2757deNot checkedno saved verdict
- 052ad6a20d375957e82a…5027f4Not checkedno saved verdict
- 76f6bc85fc9cb89bc3f9…5415eaNot checkedno saved verdict
- 741859cf238c3a63bbb2…561c2eSafetrust 85known-software reference set · not scanned here
- 47edbd3edd9123a1250c…3421d6Not checkedno saved verdict
- 76949b03f57041b07f41…10cbc3Safetrust 85known-software reference set · not scanned here
- 4fd91087253a1507a5e5…1fcf1aNot checkedno saved verdict
- ada1a52064ee93ebe6f8…77c705Safetrust 85known-software reference set · not scanned here
- 76efe571adda7aed467f…789caaSafetrust 85known-software reference set · not scanned here
- eb9b262e4d179268e6f0…6a1c45Safetrust 85known-software reference set · not scanned here
Chapter 04
Technical details
2 of the 69 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 2
The saved verdict treats these detections as likely false positives.
- APEXMalicious
- BkavW32.Malware.C152E8C0
File fingerprint
- Last analyzed
- Nov 18, 2026, 12:19 AM UTC
- SHA-256
7f59a41a8b6dabd119c6bac2fcaf09de1f45e73c35001d469f82babb7f7b9bee- SHA-1
d196a8c8d9f1835030470d4cbac7b7e1eb30bc94- MD5
b199fd96523e251604a2655db1311405
About this file
IRUS_V6.7.5.exe is a Win32 EXE file of 64.0 MB.
- Type and size
- Win32 EXE · 64.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 18, 2025On VirusTotal.
- Submitted by
- 3,420 distinct sources
- Packer
- None detected
- Entropy
- 6.40 of 8
First scanned
Antivirus consensus
2 of 69 engines flagged this file
6 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.
- Tier-118 engines0flagged
- Tier-235 engines0flagged
- Low-trust16 engines2flagged
View all 75 engine results
- APEXMalicious: Malicious
- BkavMalicious: W32.Malware.C152E8C0
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetNo result
- DeepInstinctClean
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
PE forensics
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.
Prevalence
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is IRUS_V6.7.5.exe safe?
What is IRUS_V6.7.5.exe?
How many antivirus engines detected IRUS_V6.7.5.exe?
What is the SHA-256 hash of IRUS_V6.7.5.exe?
Is it safe to run IRUS_V6.7.5.exe?
How up to date is this analysis of IRUS_V6.7.5.exe?
Community
Member reviews and reports for this exact file hash.