File scan report
Verdict Safe
Is Rim
Single less reliable engine flag on an unsigned executable with clean sandbox and no malicious files it created.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file can be executed with standard precautions; the single less reliable flag is consistent with known false-positive patterns for unsigned utilities.
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
1 of 53 flagged
- Flagged 1
- No detection 52
- No result 22
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
One less reliable engine (APEX) flagged the file while 74 others remained silent. Sandbox execution showed only routine behaviour, no malicious files it created were dropped, and the single contacted host is not known-malicious.
The detection pattern matches the classic less reliable-only false-positive shape: 1/53 engines, no major antivirus engines flagged it, only less reliable engines flagged it. The file is unsigned, yet no major antivirus engines raised an alarm and sandbox analysis returned no offensive techniques or malicious verdicts. Ten files it created were inspected and none flagged malicious. The single external IP contacted is not present in our malicious-host cache.
What We Detected
The antivirus engines recorded a single less reliable detection (APEX) against an otherwise clean 75-engine scan. No major antivirus engines flagged the sample.
Threat Behavior
Sandbox execution produced only MITRE techniques common in legitimate software and wrote ten temporary Qt/PyQt6 libraries; none of the files it created triggered malicious verdicts. The single external IP contacted is not listed in our malicious-host cache.
What To Do Now
Keep security software enabled. If the file is from an official RimWorld mod-manager distribution channel, the less reliable flag is most likely a false positive. Re-scan after any future updates.
Where this verdict could be wrong1 caveat
- similarHashes returned 1 prior 'suspicious' verdict on import-table fingerprint match (signerCoMatch=false) — weak signal due to framework collision
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 74/53 engines returned clean or undetected
- Sandbox produced no malicious verdict
- No malicious files it created
- no complete contacted-host reputation result was available contacted
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- 17sandbox rule tags
- 3spawned processes
- 1network contact
- 16filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
17MITRE 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
- T1027.009· Obfuscated code
- T1033· Reads user info
- T1045
- T1057· Lists programs
- T1059· Runs commands
- T1063
- T1070.006· Covers its tracks
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1129· Loads modules
- T1140· Deobfuscation
- T1497· Sandbox evasion
- T1497.001· Sandbox evasion
- T1574· Execution hijack
Observed activity
Processes started
3Programs the file ran, with their command lines.
RimModManager-Windows-x64.exe"C:\Users\<USER>\Desktop\RimModManager-Windows-x64.exe"RimModManager-Windows-x64.exeRimModManager-Windows-x64.exe"C:\Users\user\Desktop\RimModManager-Windows-x64.exe"
Network contacts
11 host, listed as 3 links. Links show the host and path only.
- URL
http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl - URL
http://crl.microsoft.com/pki/crl/products/WinPCA.crl - URL
http://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl
Files
15Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_1.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_2.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Core.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Gui.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Network.dll
Show all 15 entries for files
- Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Pdf.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Svg.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Widgets.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\VCRUNTIME140.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\VCRUNTIME140_1.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\opengl32sw.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\plugins\generic\qtuiotouchplugin.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\plugins\iconengines\qsvgicon.dll - Written
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\plugins\imageformats\qgif.dll
Mutexes
1Named locks a program uses so only one copy runs; malware families often reuse them.
Local\SessionImmersiveColorMutex
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
162.159.36.2
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.
- c20ad45b3c2891d9f7a5…b3e43dNot checkedno saved verdict
- a4a6f28f2be50a9698c4…2326d8Not checkedno saved verdict
- b4015c5d519b4fe93c00…2feae7Not checkedno saved verdict
- c585918fb1d4821a054e…ac7e8fNot checkedno saved verdict
- 8c98b5ee246e18397d0d…5b34deNot checkedno saved verdict
- f41e33e1d790bd0d3eb1…e66867Not checkedno saved verdict
- 005b0aa0c9a5b930dfdd…bea13dNot checkedno saved verdict
- 81da2f88cd624097581f…542d28Not checkedno saved verdict
- fc9e4146f33be3d09b23…3a61a7Not checkedno saved verdict
- c4f03a873f96edd8ab9c…8319c7Not checkedno saved verdict
Chapter 04
Technical details
1 of the 53 antivirus engines that checked it flags 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 1
The saved verdict treats these detections as likely false positives.
- APEXMalicious
File fingerprint
- Last analyzed
- Sep 1, 2026, 8:21 PM UTC
- SHA-256
e7fbcf164517b99bf2693db9e6ef3ca0ebba8b436f594c0cff56b11637ac364a- SHA-1
b3d481e0de493fe1edbde5499b1d1a530455cf53- MD5
91a21b40b17065518ef909b85b624dd3
About this file
RimModManager-Windows-x64.exe is a Win32 EXE file of 38.8 MB.
- Type and size
- Win32 EXE · 38.8 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 29, 2026On VirusTotal.
- Submitted by
- 4 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Antivirus consensus
1 of 53 engines flagged this file
22 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-18 engines0flagged
- Tier-232 engines0flagged
- Low-trust13 engines1flagged
View all 75 engine results
- APEXMalicious: Malicious
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- ArcabitClean
- AvastNo result
- Avast-MobileNo result
- AVGNo result
- AviraClean
- BitDefenderNo result
- BitDefenderFalxNo result
- BkavNo result
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetNo result
- DeepInstinctClean
- DrWebNo result
- ElasticClean
- EmsisoftClean
- ESET-NOD32No result
- F-SecureNo result
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminNo result
- K7AntiVirusClean
- K7GWClean
- KasperskyNo result
- KingsoftNo result
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaNo result
- RisingNo result
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSNo result
- TrendMicroNo result
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- 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 RimModManager-Windows-x64.exe safe?
What is RimModManager-Windows-x64.exe?
How many antivirus engines detected RimModManager-Windows-x64.exe?
What is the SHA-256 hash of RimModManager-Windows-x64.exe?
Is it safe to run RimModManager-Windows-x64.exe?
How up to date is this analysis of RimModManager-Windows-x64.exe?
Community
Member reviews and reports for this exact file hash.