Is anvirrus.exe safe?
Signed NSIS installer with 4 tier-1 detections on IObit family and observed process-injection techniques.
14 of 74 engines flag the file, including 4 tier-1 engines converging on IObit-related labels. The binary is signed by an unknown publisher, exhibits process-injection and privilege-escalation behaviour, yet shows no malicious child files or confirmed C2 infrastructure.
0bd3193b8d956fab39…265b69d0d1bcc7Recommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
14 of 74 engines flag the file, including 4 tier-1 engines converging on IObit-related labels. The binary is signed by an unknown publisher, exhibits process-injection and privilege-escalation behaviour, yet shows no malicious child files or confirmed C2 infrastructure.
The combination of tier-1 detections, offensive MITRE techniques, and a malware-sharing site listing outweighs the absence of malicious dropped children and clean community comments. Lack of signer history prevents treating the certificate as a strong trust signal. The file therefore sits in mixed-signal territory rather than a clear safe or malicious classification.
What We Detected
Four tier-1 engines (DrWeb, ESET-NOD32, Fortinet, Sophos) and ten additional engines label the sample as IObit-related or generic unwanted software. Runtime evidence shows process injection (T1055), token manipulation (T1134), service creation (T1543.003), and defense-evasion (T1562.001). The NSIS-built executable writes multiple temporary files and contacts direct IP addresses without domain names.
Threat Behavior
Observed actions are consistent with potentially unwanted system-modification utilities rather than data-theft or ransomware payloads. No sandbox flagged the execution as malicious, and none of the ten dropped children carry independent malicious verdicts. The certificate is valid but belongs to an entity with no prior reputation in our dataset.
What To Do Now
Do not run the file on production systems. If the binary is required, execute it only in an isolated virtual machine and monitor for unexpected service installations or registry changes. Keep endpoint protection enabled; the mixed signals warrant continued scrutiny rather than outright trust.
Where this verdict could be wrong3 caveats
- prevalence.classification='common_old' with 13152 submissions suggests widespread distribution rather than targeted malware.
- contactedHosts.inspected=2 with 0 maliciousHosts and 0 suspiciousHosts — no confirmed malicious infrastructure contact.
- communityComments contain multiple 'Clean' verdicts with scores 0-2/100 citing valid certificate.
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 dropped children
- no malicious sandbox verdict
- common_old prevalence
- tier-1 detections on IObit family
- offensive MITRE techniques observed
- unknown signer with no history
- direct-IP network traffic
Treat as potentially unwanted software; run only under controlled conditions and monitor system changes.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete14 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete2 signature or behavior rules matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 27MITRE ATT&CK techniques
- 15spawned processes
- 22network contacts
- 40filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Created or modified a scheduled task, which can provide persistence.
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
anvirrus.exe
0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\file.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nskD775.tmp
C:\Users\<USER>\AppData\Local\Temp\nskD775.tmp
04Isolated runtime analysis - Written fileObserved
nsc3.tmp
C:\Documents and Settings\Administrator\Local Settings\Temp\nsc3.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
13.107.4.50
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
192.168.0.92
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 13.107.4.50
- 192.168.0.92
- a83f:8110:ffff:ffff:ffff:ffff:ffff:ffff
- 72.21.81.240
- a83f:8110:584a:b5b1:17cb:1ec8:0:0
- 192.168.0.67
- 23.216.147.64
- a83f:8110:6400:0:4e00:6f00:7400:4500
- 192.168.0.45
- a83f:8110:ffff:ffff:100:0:a003:7100
- http://crt.usertrust.com/USERTrustRSAAddTrustCA.crt
- http://ctldl.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab?886200ad0d7d4152
- C:\Users\<USER>\AppData\Local\Temp\nskD775.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsc3.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsl3.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\nsx3.tmp
- C:\Documents and Settings\Administrator\Local Settings\Temp\nss3.tmp
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A68.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A69.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B53.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BA3.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1B63.tmp.csv
- oleacc-msaa-loaded
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- e6a7f1f8810e46a736e8…2c1544Never scannednever seen before
- 027f58ea864ae1bffbb0…430ca0Never scannednever seen before
- dea37666ea6a0d73741e…9e883dNever scannednever seen before
- 1a262f697dbddc8d2c7c…c63dfbNever scannednever seen before
- 2099f0854585b2115e09…0d7b95Never scannednever seen before
- 3096d8e82917a9b73f32…3cdd5bNever scannednever seen before
- 30e621d2720a1f8b727f…44e8bcNever scannednever seen before
- f2f69d75c8e2d790026c…f926e9Never scannednever seen before
- 67f193c7b2edcd0c93ef…bbaa2dNever scannednever seen before
- 4d5434fc95c38b74a2ac…fea714Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 2rule hits recorded
- 14 / 74engines flagged
- 3,658sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
14 of 74 antivirus engines flagged the file, including alibabacloud and Antiy-AVL.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 3,658 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: anvirrus.exe — 0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\file.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nskD775.tmp — C:\Users\<USER>\AppData\Local\Temp\nskD775.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: nsc3.tmp — C:\Documents and Settings\Administrator\Local Settings\Temp\nsc3.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.4.50 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 192.168.0.92 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
One or more independent reference databases matched this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Users\<USER>\Desktop\program.exe"The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence13.107.4.50 · a83f:8110:ffff:ffff:ffff:ffff:ffff:ffff · 72.21.81.240
14 of 74 engines flagged this file
View all 74 engine results
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.
Fingerprint and provenance
- File name
- anvirrus.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Global Security Center
- Size
- 4.2 MB
- Last analyzed
- Jul 25, 2026, 4:06 PM UTC
0bd3193b8d956fab39534d42c2c7768d7867085642e1128221265b69d0d1bcc7Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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?
How do I remove anvirrus.exe?
What kind of malware is 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.