File scan report
Verdict Suspicious
Is anvirrus. exe safe? Treat it as suspicious.
This signed NSIS installer is flagged by 14 of the 69 antivirus engines that checked it, mostly as a potentially unwanted IObit-related program, with no high-risk behaviour…
Read the whole reasonShow less
Why Suspicious? 14 antivirus engines flag it and a reference database lists it as malicious.
Moderate evidence · More than one sign points to a problem, but nothing confirms it is harmful.
Do not install this program unless you deliberately sought it from a source you trust. If it appeared unexpectedly, remove it and run a full scan with your protection enabled.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (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
14 of 69 flagged
- Flagged 14
- No detection 55
- No result 5
- Code signing Global Security Center
- Test run Completed
- First seen 5y 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
Several major antivirus engines, including ESET, Fortinet and DrWeb, label this installer a potentially unwanted or riskware program linked to IObit. It carries a valid signature from Global Security Center, a signer with almost no history with us, and the sandbox runs showed no high-risk techniques. It looks more like unwanted software than outright malware.
Fourteen of the 69 antivirus engines that checked it flag the file, including four major antivirus engines. Three of those four use potentially-unwanted or riskware labels tied to IObit. Backdoor labels come only from less reliable engines, while Sophos reports a generic malware detection. The valid signature belongs to a publisher with only one prior sample in our records, so it offers little reassurance. The sandbox runs recorded only techniques common in legitimate software, with no injection targets or hostile network contacts. The file is widely submitted and was first seen on Aug 8, 2021, which fits bundled or unwanted software better than a targeted threat.
What We Detected
14 of the 69 antivirus engines that checked it flagged this NSIS installer. ESET (Win32/IObit.BH potentially unwanted application), Fortinet (Riskware/IObit) and DrWeb (Program.Unwanted) treat it as unwanted software, and Sophos reports a generic malware label. A few less reliable engines use backdoor or dropper labels. The file is validly signed by Global Security Center, a publisher with almost no history in our records.
Threat Behavior
The sandbox runs recorded only techniques common in legitimate installers, with no named injection target and no malicious network contacts among the hosts we checked. The file has been widely submitted since Aug 8, 2021.
What To Do Now
Avoid installing this program unless you obtained it intentionally from its official source. If it is already installed and you did not choose it, uninstall it and run a full scan with your security software kept enabled.
Where this verdict could be wrong2 caveats
- The file is widely distributed and has been seen since 2021, and no high-risk behaviour in the test run was recorded, which argues against a backdoor.
- Less reliable engines label it a backdoor and Sophos gives a generic malware label, so a more harmful payload cannot be fully excluded.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Valid code signature
- Widely submitted since 2021 by thousands of sources
- No high-risk techniques or injection targets recorded when it ran
- Four major antivirus engines flag the file, three of them as potentially unwanted or riskware software
- Some engines use backdoor or dropper labels
- The signing publisher has almost no history in our records
6 sources checked · 5 complete · 1 partial. 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- 27sandbox rule tags
- 3spawned processes
- 3network contacts
- 40filesystem & 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: Used an unusual way to talk to a server.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the network settings of the test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as creating a scheduled task; none was recorded.
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
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.
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 7: FileSeen in the test run
anvirrus.exe
0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\Desktop\program.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
file.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
nskD775.tmp
C:\Users\<USER>\AppData\Local\Temp\nskD775.tmp
Test run - Evidence 5 of 7: Written fileSeen in the test run
nsc3.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\nsc3.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
72.21.81.240
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.40.197.194
Contacted during the test run.
Test run - +1 more recorded observation
7 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
27MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1016· Network recon
- T1018
- T1027· Obfuscated code
- T1036
- T1053· Scheduled task
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1112
- T1115
- T1125
- T1129· Loads modules
- T1134
- T1222
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1529
- T1543.003· Service install
- T1547.009· Auto-start
- T1562.001· Disables security
- T1574.002· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
program.exe"C:\Users\<USER>\Desktop\program.exe"file.exe%SAMPLEPATH%\file.exe0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7.exe%SAMPLEPATH%\0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7.exe
Network contacts
33 hosts, listed as 2 addresses, 1 link. Links show the host and path only.
- IP address
72.21.81.240 - IP address
23.40.197.194 - URL
http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
Files
30Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\nskD775.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsc3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsl3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsx3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nss3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsv3.tmp
Show all 30 entries for files
- Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nso3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsu3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsn3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsg3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsa3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsm3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nst3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsd3.tmp - Written
C:\Documents and Settings\Administrator\Local Settings\Temp\nsb3.tmp - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A68.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A69.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B53.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BA3.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B63.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BA4.tmp.txt - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2100.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER21AC.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER21DC.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER267F.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2690.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2691.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERE251.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WERE4A3.tmp.csv
Registry and auto-start
5Settings the file changed, including ways to start again after a restart.
- Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Counter - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Help - Deleted
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Object List
Mutexes
10Named locks a program uses so only one copy runs; malware families often reuse them.
oleacc-msaa-loadedCTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Show all 10 entries for mutexes
CTF.TimListCache.FMPDefaultS-1-5-21-1482476501-1645522239-1417001333-500MUTEX.DefaultS-1-5-21-1482476501-1645522239-1417001333-500MSCTF.Shared.MUTEX.EBHLocal\MSCTF.Asm.MutexDefault1\BaseNamedObjects\Local\SM0:2572:168:WilStaging_02
Sandbox background — not the file
31The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM process
updater.exeC:\Program Files (x86)\Google3708_1003737683\bin\updater.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google920_156310282\bin\updater.exe - VM process
updater.exeC:\Program Files\Google1820_1737239004\bin\updater.exe - VM process
updater.exeC:\Program Files\Google2780_213475321\bin\updater.exe
Show all 31 entries for sandbox background — not the file
- VM process
updater.exeC:\Program Files\Google2596_104901433\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3048_1534747208\bin\updater.exe - VM process
updater.exeC:\Program Files\Google948_417788922\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3828_1022329632\bin\updater.exe - VM process
updater.exeC:\Program Files\Google4084_416325984\bin\updater.exe - VM process
updater.exeC:\Program Files\Google4064_1995471066\bin\updater.exe - VM host
13.107.4.50 - VM host
192.168.0.92 - VM host
a83f:8110:ffff:ffff:ffff:ffff:ffff:ffff - VM host
a83f:8110:584a:b5b1:17cb:1ec8:0:0 - VM host
192.168.0.67 - VM host
23.216.147.64 - VM host
a83f:8110:6400:0:4e00:6f00:7400:4500 - VM host
192.168.0.45 - VM host
a83f:8110:ffff:ffff:100:0:a003:7100 - VM host
23.216.147.76 - VM host
a83f:8110:6900:7300:6100:6200:6c00:6500 - VM host
a83f:8110:106:0:0:5:5000:0 - VM host
a83f:8110:0:0:9800:0:0:0 - VM host
a83f:8110:0:0:8a01:0:0:0 - VM host
52.251.79.25 - VM host
131.253.33.203 - VM host
20.80.129.13 - VM host
20.99.132.105 - VM URL
http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab
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.
- e6a7f1f8810e46a736e8…2c1544Not checkedno saved verdict
- 027f58ea864ae1bffbb0…430ca0Not checkedno saved verdict
- dea37666ea6a0d73741e…9e883dNot checkedno saved verdict
- 1a262f697dbddc8d2c7c…c63dfbNot checkedno saved verdict
- 2099f0854585b2115e09…0d7b95Not checkedno saved verdict
- 3096d8e82917a9b73f32…3cdd5bNot checkedno saved verdict
- 30e621d2720a1f8b727f…44e8bcNot checkedno saved verdict
- f2f69d75c8e2d790026c…f926e9Not checkedno saved verdict
- 67f193c7b2edcd0c93ef…bbaa2dNot checkedno saved verdict
- 4d5434fc95c38b74a2ac…fea714Not checkedno saved verdict
Chapter 04
Technical details
14 of the 69 antivirus engines that checked it flag it; signed by Global Security Center.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 14
- DrWeb (major engine)Program.Unwanted.4485
- ESET-NOD32 (major engine)Win32/IObit.BH potentially unwanted application
- Fortinet (major engine)Riskware/IObit
- Sophos (major engine)Mal/Generic-S
- alibabacloudBackdoor:Win/Tinukebot.AC
- Antiy-AVLGrayWare/Win32.IObit
- CrowdStrikewin/grayware_confidence_90% (W)
- CylanceUnsafe
File fingerprint
- Last analyzed
- Jul 25, 2026, 4:06 PM UTC
- SHA-256
0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7- SHA-1
f4f71527cb64e97d1c5b543b2984b48b3528a196- MD5
8072fb2063bf9a74d3d9c4e23e859064
About this file
anvirrus.exe is a Win32 EXE file of 4.4 MB.
- Type and size
- Win32 EXE · 4.4 MB
- Signer
- Global Security CenterValid code signature.
- First seen
- Aug 8, 2021On VirusTotal.
- Submitted by
- 3,658 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Antivirus consensus
14 of 69 engines flagged this file
5 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines4flagged
- Tier-235 engines3flagged
- Low-trust17 engines7flagged
View all 74 engine results
- alibabacloudMalicious: Backdoor:Win/Tinukebot.AC
- Antiy-AVLMalicious: GrayWare/Win32.IObit
- CrowdStrikeMalicious: win/grayware_confidence_90% (W)
- CylanceMalicious: Unsafe
- DrWebMalicious: Program.Unwanted.4485
- ESET-NOD32Malicious: Win32/IObit.BH potentially unwanted application
- FortinetMalicious: Riskware/IObit
- huorongMalicious: Trojan/Foidan
- MaxSecureMalicious: Trojan.Malware.351590730.susgen
- PaloaltoMalicious: generic.ml
- RisingMalicious: Backdoor.Agent!1.663A (C64:YzY0Opqj0M3yjyxi)
- SophosMalicious: Mal/Generic-S
- VBA32Malicious: Adware.Vigua
- ZillyaMalicious: Dropper.Injector.Win32.93581
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- ALYacClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CTXClean
- CynetClean
- ElasticClean
- EmsisoftClean
- F-SecureClean
- GDataClean
- GoogleClean
- GridinsoftClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PandaClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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
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 7 questions people ask most about this file.
Is anvirrus.exe safe, or is it malware?
What is anvirrus.exe?
How many antivirus engines detected anvirrus.exe?
What should I do if I already ran anvirrus.exe?
Is anvirrus.exe digitally signed?
What is the SHA-256 hash of anvirrus.exe?
How up to date is this analysis of anvirrus.exe?
Community
Member reviews and reports for this exact file hash.