Is RimModManager-Windows-x64.exe safe?
Single low-trust engine flag on an unsigned executable with clean sandbox and no malicious children.
One low-trust engine (APEX) flagged the file while 74 others remained silent. Sandbox execution showed only ambient behaviour, no malicious children were dropped, and the single contacted host is not known-malicious.
e7fbcf164517b99bf2…56b11637ac364aRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
One low-trust engine (APEX) flagged the file while 74 others remained silent. Sandbox execution showed only ambient behaviour, no malicious children were dropped, and the single contacted host is not known-malicious.
The detection pattern matches the classic low-trust-only false-positive shape: 1/75 engines, tier1Malicious=0, onlyLowTrustFlagging=true. The file is unsigned, yet no tier-1 engine raised an alarm and sandbox analysis returned no offensive techniques or malicious verdicts. Ten dropped children were inspected and none flagged malicious. The single external IP contacted is not present in our malicious-host cache.
What We Detected
Our antivirus network recorded a single low-trust detection (APEX) against an otherwise clean 75-engine scan. No tier-1 engines flagged the sample.
Threat Behavior
Sandbox execution produced only ambient MITRE techniques and wrote ten temporary Qt/PyQt6 libraries; none of the dropped children triggered malicious verdicts. The single external IP contacted is not listed in our malicious-host cache.
What To Do Now
Keep endpoint protection enabled. If the file is from an official RimWorld mod-manager distribution channel, the low-trust 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 imphash 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/75 engines returned clean or undetected
- Sandbox produced no malicious verdict
- No malicious dropped children
- no complete contacted-host reputation result was available contacted
The file can be executed with standard precautions; the single low-trust flag is consistent with known false-positive patterns for unsigned utilities.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule 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
- 17MITRE ATT&CK techniques
- 3spawned processes
- 4network contacts
- 16filesystem & mutex artifacts
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
RimModManager-Windows-x64.exe
e7fbcf164517b99bf2693db9e6ef3ca0ebba8b436f594c0cff56b11637ac364a
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\RimModManager-Windows-x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
RimModManager-Windows-x64.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
MSVCP140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140.dll
04Isolated runtime analysis - Written fileObserved
MSVCP140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_1.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
crl.microsoft.com
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.
- 162.159.36.2
- http://crl.microsoft.com/pki/crl/products/microsoftrootcert.crl
- http://crl.microsoft.com/pki/crl/products/WinPCA.crl
- http://crl.microsoft.com/pki/crl/products/MicrosoftTimeStampPCA.crl
- C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_2.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Core.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\Qt6Gui.dll
- Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c20ad45b3c2891d9f7a5…b3e43dNever scannednever seen before
- a4a6f28f2be50a9698c4…2326d8Never scannednever seen before
- b4015c5d519b4fe93c00…2feae7Never scannednever seen before
- c585918fb1d4821a054e…ac7e8fNever scannednever seen before
- 8c98b5ee246e18397d0d…5b34deNever scannednever seen before
- f41e33e1d790bd0d3eb1…e66867Never scannednever seen before
- 005b0aa0c9a5b930dfdd…bea13dNever scannednever seen before
- 81da2f88cd624097581f…542d28Never scannednever seen before
- fc9e4146f33be3d09b23…3a61a7Never scannednever seen before
- c4f03a873f96edd8ab9c…8319c7Never 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.
- 1rule hit recorded
- 1 / 75engines flagged
- 4sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 of 75 antivirus engines flagged the file, including APEX.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 4 times from 4 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: RimModManager-Windows-x64.exe — e7fbcf164517b99bf2693db9e6ef3ca0ebba8b436f594c0cff56b11637ac364a
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\RimModManager-Windows-x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — RimModManager-Windows-x64.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: MSVCP140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: MSVCP140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI51762\PyQt6\Qt6\bin\MSVCP140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: crl.microsoft.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
1 of 75 engines flagged this file
View all 75 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- RimModManager-Windows-x64.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 37.0 MB
- Last analyzed
- Sep 1, 2026, 8:21 PM UTC
e7fbcf164517b99bf2693db9e6ef3ca0ebba8b436f594c0cff56b11637ac364aSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Run it only when it came from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.