File scan report
Verdict Safe
Is Monster
None of the 55 antivirus engines that checked it flagged the executable, while completed runtime and static checks found no corroborated malware activity, packing, persistence…
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 55 flagged
- Flagged 0
- No detection 55
- No result 20
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 55 antivirus engines that checked it detected the executable, and the completed sandbox run returned clean without high-risk techniques, persistence, or dropped files. The unsigned status and injection-related runtime mapping warrant ordinary caution, but they lack corroboration from detections, hostile hosts, or malware-specific research rules.
None of the 55 antivirus engines that checked it flagged the sample, including the contributing major antivirus engines. One completed sandbox run returned clean and recorded no high-risk techniques, persistence indicators, written files, or files it created. All ten distinct observed hosts received complete reputation coverage, with none identified as malicious or suspicious; the Microsoft domain and private address were sandbox background contacts rather than sample evidence. Static PE analysis found neither high-entropy code nor a recognized packer, and malware-specific external research produced no matches. The file is unsigned and the sandbox recorded an injection-related mapping, but those concerns are not corroborated by detections or hostile infrastructure. A suspicious prior file shares only the import-table fingerprint without signer corroboration, making that similarity weak evidence.
What We Detected
None of the 55 antivirus engines that checked it flagged MonsterCamp.exe. The antivirus analysis found no recognized packer, no high-entropy code, no brand mismatch, and no malware-specific external research matches.
Threat Behavior
One completed sandbox run returned clean. It recorded three broadly applicable techniques, including T1574.002 and injection into an updater process, but no high-risk techniques, persistence indicators, written files, or files it created. Reputation coverage included all ten distinct observed hosts and found none malicious or suspicious; the Microsoft domain and private address were identified as sandbox background traffic.
What To Do Now
The evidence does not substantiate malware activity. Because the executable is unsigned, obtain it from a trusted source, verify its SHA-256 as 70e6a7e778c2d33b67be78b8c57ea3067c13229e7f1d1377eb509e54e8001d27, and keep security software enabled when running it.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so publisher identity and certificate history cannot provide additional assurance.
- The sandbox mapped and recorded injection into an updater process, although it found no high-risk techniques and returned a clean result.
- One unrelated file sharing this import-table fingerprint previously received a suspicious assessment, but the match lacks signer corroboration and may reflect a common build framework.
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 55 antivirus engines that checked it flagged the file.
- The completed sandbox run returned clean and found no high-risk techniques, persistence, or files it created.
- Complete reputation coverage of the ten observed hosts found no malicious or suspicious infrastructure.
- The antivirus analysis found no recognized packing or high-entropy code.
- No malware-specific external research rules matched the sample.
- The executable has no digital signature, so its publisher cannot be authenticated.
- The sandbox mapped an injection-related technique and recorded interaction with an updater process, although no malicious follow-on activity was observed.
- A different unsigned executable sharing the same import-table fingerprint previously received a suspicious assessment, but this may be a build-framework collision.
6 sources checked · all complete. 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- 3sandbox rule tags
- 1spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
3MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1071· Application protocol
- T1082· System recon
- T1574.002· Execution hijack
Observed activity
Processes started
1Programs the file ran, with their command lines.
70e6a7e778c2d33b67be78b8c57ea3067c13229e7f1d1377eb509e54e8001d27.exe%SAMPLEPATH%\70e6a7e778c2d33b67be78b8c57ea3067c13229e7f1d1377eb509e54e8001d27.exe
Files
15Files the file created, changed or deleted.
- Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C0.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER29B.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2DA.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3F3.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER404.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER415.tmp.txt
Show all 15 entries for files
- Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2AA5.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2B70.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER2BAF.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3787.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3788.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER3798.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1BB1.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1C7C.tmp.csv
Registry and auto-start
20Settings the file changed, including ways to start again after a restart.
- Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\ndis.sys[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\System32\Drivers\portcls.SYS[PortclsMof] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\ACPI.sys.mui[ACPIMOFResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\HDAudBus.sys[HDAudioMofName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\System32\Drivers\en-US\portcls.SYS.mui[PortclsMof] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\advapi32.dll[MofResourceName]
Show all 20 entries for registry and auto-start
- Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\en-US\advapi32.dll.mui[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\mssmbios.sys.mui[MofResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\en-US\HDAudBus.sys.mui[HDAudioMofName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\ndis.sys.mui[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\en-US\intelppm.sys.mui[PROCESSORWMI] - Set
HKLM\Software\Microsoft\WBEM\WDM\IDE\DiskAMDX_HARDDISK___________________________2.5+____\5&2770a7af&0&0.0.0_0-{05901221-D566-11d1-B2F0-00A0C9062910} - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\intelppm.sys[PROCESSORWMI] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\ACPI.sys[ACPIMOFResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\monitor.sys[MonitorWMI] - 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
Sandbox background — not the file
15The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google876_569102644\bin\updater.exe - VM injection target
C:\Program Files\Google876_569102644\bin\updater.exe - VM host
www.microsoft.com - VM host
a83f:8110:584a:b5b1:17cb:1ec8:0:0
Show all 15 entries for sandbox background — not the file
- VM host
20.99.132.105 - VM host
23.216.147.64 - VM host
20.99.133.109 - VM host
192.229.211.108 - VM host
a83f:8110:0:0:0:0:2002:0 - VM host
20.99.184.37 - VM host
a83f:8110:7d8:ffff:e00:0:0:0 - VM host
192.168.0.45 - VM host
23.55.140.42
Chapter 04
Technical details
None of the 55 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.
File fingerprint
- Last analyzed
- Oct 14, 2026, 7:26 PM UTC
- SHA-256
70e6a7e778c2d33b67be78b8c57ea3067c13229e7f1d1377eb509e54e8001d27- SHA-1
dfca6a48fac70aef7e8a6e81f313fd258166e63f- MD5
264f9431b170c57353e23529521fbd3a
About this file
MonsterCamp.exe is a Win32 EXE file of 640.0 kB.
- Type and size
- Win32 EXE · 640.0 kB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 22, 2020On VirusTotal.
- Submitted by
- 74 distinct sources
- Packer
- None detected
- Entropy
- 4.00 of 8
First scanned
Antivirus consensus
0 of 55 engines flagged this file
20 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-19 engines0flagged
- Tier-230 engines0flagged
- Low-trust16 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealNo result
- ClamAVNo result
- CMCNo result
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32No result
- F-SecureClean
- FortinetNo result
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaNo result
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSNo result
- TrendMicroNo result
- TrendMicro-HouseCallNo result
- TrustlookNo result
- VaristClean
- VBA32No result
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaNo result
- 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 6 questions people ask most about this file.
Is MonsterCamp.exe safe?
What is MonsterCamp.exe?
How many antivirus engines detected MonsterCamp.exe?
What is the SHA-256 hash of MonsterCamp.exe?
Is it safe to run MonsterCamp.exe?
How up to date is this analysis of MonsterCamp.exe?
Community
Member reviews and reports for this exact file hash.