MalwareTipsTools

File scan report

Scan another file

Verdict Safe

Analyzed , 7 hours ago

Is DOA5Installer.exe safe? Yes, no threats found.

Only APEX flagged this unsigned installer, while 18 leading engines remained silent and the combined sandbox verdict showed no corroborating harmful activity.

Moderate evidence · No engine flags it, but no publisher signature confirms who made it.

Run it as usual if it came from the official source

Good practice2 tips

We found nothing harmful in this file.

  1. Run it only if it came from the developer's own website or an official app store.

  2. Keep your antivirus and Windows updates switched on.

No scanner can promise a file is 100% safe.

Why we think so

Share this file report

DOA5Installer.exe: Safe — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Antivirus results

1 of 71 flagged

  • Flagged 1
  • No detection 70
  • No result 4
FileDOA5Installer.exe152.6 kBSHA-256 dc732a2f1575…744249
  • Code signing Unsigned
  • Test run Completed
  • First seen 7d ago
1 of the 71 antivirus engines that checked it flags it (APEX).

Chapter 02

Why we think so

3 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

Only 1 of the 71 antivirus engines that checked it flagged the executable, and that detection came from APEX rather than a leading engine. The combined sandbox verdict was clean, with no named injection target, malicious contact, file it created, packing, or high-risk technique recorded; however, the file is unsigned and not widely submitted.

Full reasoning

The antivirus results strongly favor a false alarm: only APEX flagged the file, while none of the leading engines did. The combined sandbox verdict was clean, and no high-risk techniques or named injection targets were recorded. Although appeared as a mapping, no corresponding injection artifact was present, so it does not demonstrate process injection. The antivirus analysis also found no packer or unusually high-entropy code. Confidence is moderated because the executable is unsigned, has only seven submitters, and its bytes were unavailable for an independent static inspection.

Detailed assessment

What We Detected

Only 1 of the 71 antivirus engines that checked it flagged this executable. APEX supplied the sole generic detection, while 18 leading engines did not flag it and no malware family was identified.

Threat Behavior

The combined sandbox verdict was clean. No high-risk technique, named injection target, network contact, file it created, or persistence indicator was recorded. A T1055 mapping lacked the artifact needed to demonstrate actual process injection. The antivirus analysis also found no packer or unusually high-entropy code.

What To Do Now

The isolated detection is most consistent with a false alarm. Because the executable is unsigned and has modest prevalence, obtain it from the expected source, keep security software enabled, and confirm its hash before running it.

Where this verdict could be wrong3 caveats
  • The executable is unsigned, so no verified publisher identity supports it.
  • Only seven distinct sources submitted the file, and it was first seen on Nov 3, 2026.
  • The uploaded bytes were not available for an independent static inspection.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

Points in its favour
  • Only 1 of the 71 antivirus engines that checked it flagged the file, and none of the 18 leading engines did.
  • The combined sandbox verdict was clean.
  • No high-risk runtime technique or named injection target was recorded.
  • No malicious network contact or file it created was observed.
  • The antivirus analysis found no packer or unusually high-entropy code.
Points against
  • The executable is unsigned, so its publisher cannot be authenticated.
  • It has only seven distinct submitters and was first seen on Nov 3, 2026.
  • The file bytes were unavailable for an independent static inspection.

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 4 isolated tests; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 4isolated sandbox runs
  • 21sandbox rule tags
  • 2spawned processes
  • 0network contacts
  • 12filesystem & mutex artifacts
Runtime behaviour

What this file did when executed

This file was detonated in 4 sandboxes and its runtime behaviour was observed.

1 clean detonation

Sandbox verdicts

1
  • VT: CLEANclean

Techniques observed in the sandbox

21

MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.

  • T1027· Obfuscated code
  • T1033· Reads user info
  • T1036
  • T1055· Process injection
  • T1056.001· Keylogging
  • T1057· Lists programs
  • T1069
  • T1082· System recon
  • T1083· Scans your files
  • T1129· Loads modules
  • T1222
  • T1485
  • T1497· Sandbox evasion
  • T1518· Checks your AV
  • T1547.009· Auto-start
  • T1548
  • T1553
  • T1553.002
  • T1564.003· Hides artifacts
  • T1574· Execution hijack
  • T1614.001

Observed activity

Processes started
2

Programs the file ran, with their command lines.

  • DOA5Installer.exe"C:\Users\<USER>\Desktop\DOA5Installer.exe"
  • DOA5Installer.exe"C:\Users\user\Desktop\DOA5Installer.exe"
Files
2

Files the file created, changed or deleted.

  • WrittenC:\Users\user\AppData\Local\Microsoft\Windows\Caches
  • WrittenC:\Users\user\AppData\Local\Microsoft\Windows\Explorer
Registry and auto-start
4

Settings the file changed, including ways to start again after a restart.

  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browse For Folder Width
  • SetHKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Browse For Folder Height
  • SetHKEY_CURRENT_USER\Software\Classes\Local Settings\MuiCache\7b\52C64B7E\@C:\Windows\system32\NetworkExplorer.dll,-2
  • SetHKEY_CURRENT_USER\Software\Microsoft\OneDrive\Accounts\LastUpdate
Mutexes
10

Named locks a program uses so only one copy runs; malware families often reuse them.

  • Global\OneSettingQueryMutex+compat+encapsulation
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_idx.db!rwWriterMutex
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_16.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_32.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_48.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_96.db!dfMaintainer
Show all 10 entries for mutexes
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_256.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_768.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_1280.db!dfMaintainer
  • \Sessions\1\BaseNamedObjects\Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:iconcache_1920.db!dfMaintainer
Sandbox background — not the file
7

The analysis machine's own processes and connections, recorded in every run.

  • VM processservices.exeC:\Windows\system32\services.exe
  • VM processsvchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time
  • VM processsvchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
  • VM processlsass.exeC:\Windows\system32\lsass.exe
Show all 7 entries for sandbox background — not the file
  • VM processsvchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p

Chapter 04

Technical details

1 of the 71 antivirus engines that checked it flags 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompleteWorth noting: 1 of 71 engines flagged it · 4 gave no result · treated as non-decisive Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxComplete4 runs: 1 clean, 3 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerNot neededThe sandbox recorded no contacted hosts to checkNo date recorded
Signature rulesYARAify community rules + MalwareTips rulesComplete1 MalwareTips behaviour rule Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 1

The saved verdict treats these detections as likely false positives.

  • APEXMalicious

File fingerprint

Last analyzed
Nov 10, 2026, 10:19 PM UTC
SHA-256
dc732a2f157579cf85208a1546d099b7a88936125c78e055e55ba68c19744249
SHA-1
86a9385a9623dc372fdc8b1d80484b65a450c796
MD5
a8377bde81f1da3525f0284013fda4fe

About this file

DOA5Installer.exe says it is DOAReborn mod installer for DOA5LR (DOA5Installer), 152.6 kB.

Claims to be
DOAReborn mod installer for DOA5LR (DOA5Installer)From the file's own version information, written by whoever built it.
Original name
DOA5Installer.exeMatches the shared file name.
Type and size
Win32 EXE · 152.6 kB
Signer
UnsignedNo code signature.
First seen
Nov 3, 2026On VirusTotal.
Submitted by
7 distinct sourcesRarely seen: few people have submitted this exact file.
Packer
None detected
Entropy
5.47 of 8

First scanned

Antivirus consensus

1 of 71 engines flagged this file

1 malicious0 suspicious70 not flagged4 no result

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.

  • Tier-118 engines
    0flagged
  • Tier-236 engines
    0flagged
  • Low-trust17 engines
    1flagged
These detections were treated as likely false positives in the saved verdict.
View all 75 engine results
  • APEXMalicious: Malicious
  • AcronisClean
  • AhnLab-V3Clean
  • AlibabaClean
  • alibabacloudClean
  • ALYacClean
  • Antiy-AVLClean
  • ArcabitClean
  • AvastClean
  • Avast-MobileNo result
  • AVGClean
  • AviraClean
  • BitDefenderClean
  • BitDefenderFalxNo result
  • BkavClean
  • CAT-QuickHealClean
  • ClamAVClean
  • CMCClean
  • CrowdStrikeClean
  • CTXClean
  • CylanceClean
  • CynetClean
  • DeepInstinctClean
  • DrWebClean
  • ElasticClean
  • 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
Rule-based evidence

Signatures and behavior heuristics

Low-severity pattern matches — worth noting but not on their own cause for alarm.

1 heuristic
MITRE ATT&CK profile
Defense evasion× 1
Behavior heuristics
Deterministic patterns derived from scan data and observed runtime behavior
  • ProcessInjection
    T1055
    low

    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.

    Evidence
    T1055 (sandbox MITRE mapping)
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.

ent 5.47Unpacked
Section entropy6 sections
.text
6.31
.rdata
4.40
.data
0.34
.tls
0.00
.rsrc
3.74
.reloc
6.74
0.0Packed threshold 7.28.0
Prevalence

How widely this file has been seen

Moderate prevalence — neither rare nor common. No strong prior applies.

Medium
Unique uploaders
7
Moderate upload volume.
Total submissions
7
Includes repeat uploads by the same source.
First seen
7d ago
Nov 3, 2026
Prevalence quadrant
Rare · New
Needs evidence-led scrutiny
Common · New
Just-released software
Rare · Old
Niche or internal tooling
Common · Old
Often established software

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is DOA5Installer.exe safe?
We found nothing harmful in DOA5Installer.exe. 1 of the 71 antivirus engines that checked it flags it; after weighing the other evidence we treat that alert as false alarms. Run it only if it came from the developer's own website or an official app store.
What is DOA5Installer.exe?
DOA5Installer.exe is a Windows program, about 152.6 kB. Its version information says it is “DOAReborn mod installer for DOA5LR” (DOA5Installer). Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Nov 3, 2026.
How many antivirus engines detected DOA5Installer.exe?
1 of the 71 antivirus engines that checked it flags DOA5Installer.exe (APEX). We weigh which engines flagged it and what else the scan found, not just the count.
What is the SHA-256 hash of DOA5Installer.exe?
The SHA-256 fingerprint of DOA5Installer.exe is dc732a2f157579cf85208a1546d099b7a88936125c78e055e55ba68c19744249, and its MD5 is a8377bde81f1da3525f0284013fda4fe. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
Is it safe to run DOA5Installer.exe?
We found nothing harmful in DOA5Installer.exe. The main caveat is where you got it: attackers sometimes spread malware under the name of real software, so get it from the official website. If your own antivirus warns about it, check the source before you ignore the warning.
How up to date is this analysis of DOA5Installer.exe?
This report reflects the scan on Nov 10, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Recent reports on other files with the same rating.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.