Is Modrinth App_0.21.5_x64-setup.exe safe?
No antivirus engine detected this signed installer, but one sandbox recorded process-injection and LSASS-targeting indicators that warrant caution pending publisher verification.
All 75 antivirus engines were silent, including 17 tier-1 engines, and the installer carries a verified signature. However, one runtime report mapped activity to process injection and apparent LSASS access, while the signer lacks established history, so the file should only be obtained from the publisher’s official channel.
e8904effec07201312…601e4c27659852Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
All 75 antivirus engines were silent, including 17 tier-1 engines, and the installer carries a verified signature. However, one runtime report mapped activity to process injection and apparent LSASS access, while the signer lacks established history, so the file should only be obtained from the publisher’s official channel.
The antivirus evidence is strongly reassuring: none of 75 engines raised a detection, including all 17 tier-1 participants. One completed sandbox did not assign a malicious result, and the only observed domain received no adverse reputation result under complete contact coverage. The installer is signed by Rinth, but no historical signer record or curated publisher match is available. Runtime heuristics nevertheless recorded T1055 and apparent targeting of LSASS, which are unusual enough to prevent an unqualified benign assessment. The shared-imphash history is mixed and does not identify this file because every match lacks signer co-matching. Overall, the evidence more strongly suggests a benign installer with noisy behavioral telemetry than established malware, but source verification remains important.
What We Detected
None of 75 antivirus engines flagged the installer, and all 17 tier-1 engines that participated reported no detection. The executable has a verified signature from Rinth, is not packed, and has no high-entropy code indication. It is also broadly submitted for a file only three days old, with 208 submitters and 239 submissions.
Threat Behavior
One completed sandbox did not issue a malicious result. However, the saved telemetry mapped activity to T1055 process injection and reported apparent targeting of LSASS, which can be associated with credential access. The single observed domain, cl-glcb907925.gcdn.co, was fully covered by the host-reputation check and had no malicious or suspicious cache entry. Ten dropped files were inspected without a malicious child being identified, although their individual verdicts remain unknown.
What To Do Now
Verify that the file hash and Rinth signature match the installer offered through Modrinth’s official release channel. Keep endpoint protection enabled, and avoid running the file if the source, signature, or expected version cannot be confirmed.
Where this verdict could be wrong3 caveats
- The T1055 mapping and recorded LSASS targeting are concerning because they can indicate process injection or credential access, even though no engine or sandbox assigned a malicious label.
- The 'Rinth' signature is verified, but signing.signerStats.found=false and signing.trustedPublisher.matched=false, so historical publisher trust cannot validate it.
- All 10 dropped children have unknown individual verdicts; droppedChildren.hasMaliciousChild=false therefore provides limited reassurance rather than confirmed benign status.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines reported malicious or suspicious detections.
- 17 tier-1 engines reported no detection.
- The executable has a verified signature from 'Rinth'.
- behaviour.hasMaliciousSandboxVerdict=false in the one completed sandbox.
- The fully covered observed host and 10 inspected dropped children produced no confirmed malicious result.
- Runtime telemetry mapped activity to MITRE T1055 process injection.
- A heuristic reported process activity targeting lsass.exe.
- The verified 'Rinth' signer has no historical sample record in signing.signerStats.
- All 10 inspected dropped children lack individual verdicts.
Download and install only after confirming the SHA-256 and Rinth signature against Modrinth’s official release channel. Keep antivirus and endpoint protection enabled during installation and use.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Complete1 contacted host was cross-checked.
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
- 24MITRE ATT&CK techniques
- 11spawned processes
- 1network contacts
- 21filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
Modrinth App_0.21.5_x64-setup.exe
e8904effec07201312f7c850aac12d297c4255e383a77f6c6a601e4c27659852
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Modrinth App_0.21.5_x64-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nszC8FE.tmp
C:\Users\<USER>\AppData\Local\Temp\nszC8FE.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
cl-glcb907925.gcdn.co
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- cl-glcb907925.gcdn.co
- HKEY_CURRENT_USER\Software\Classes\.mrpack\(Default)
- HKEY_CURRENT_USER\Software\Classes\mrpack\(Default)
- HKEY_CURRENT_USER\Software\Classes\mrpack\DefaultIcon\(Default)
- HKEY_CURRENT_USER\Software\Classes\mrpack\shell\(Default)
- HKEY_CURRENT_USER\Software\Classes\mrpack\shell\open\(Default)
- HKEY_CURRENT_USER\Software\Classes\mrpack\shell\open\command\(Default)
- C:\Users\<USER>\AppData\Local\Temp\nszC8FE.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\nsis_tauri_utils.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\user\AppData\Local\Temp\nsh8E29.tmp
- C:\Users\user\AppData\Local\Temp\nsl72BF.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 9baee42d66f715bba878…b40256Never scannednever seen before
- 2306acbd8ff6f6837625…d5f43cNever scannednever seen before
- 37bc1f8cfe9fc066ab9a…b58cf9Never scannednever seen before
- 56b96add1978b1abba28…753fe2Never scannednever seen before
- 1210c600335146b5e9c4…cb7926Never scannednever seen before
- 38192da8b71c5a231a7f…8110c9Never scannednever seen before
- 7317e5508923f425bced…711464Never scannednever seen before
- 8dc562cda7217a3a52db…7f65a8Never scannednever seen before
- 03e8d51447be96516dd5…98900aNever scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never 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
- 0 / 75engines flagged
- 208sources 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
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The file has a valid code signature from Rinth.
ProvenanceObservedSourceCode-signing metadataObserved at - 04
Scanned file: Modrinth App_0.21.5_x64-setup.exe — e8904effec07201312f7c850aac12d297c4255e383a77f6c6a601e4c27659852
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Modrinth App_0.21.5_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nszC8FE.tmp — C:\Users\<USER>\AppData\Local\Temp\nszC8FE.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsoC90E.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: cl-glcb907925.gcdn.co — 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
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.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exe
0 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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- Modrinth App_0.21.5_x64-setup.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: Rinth
- Size
- 24.8 MB
- Last analyzed
- Sep 25, 2026, 11:03 PM UTC
e8904effec07201312f7c850aac12d297c4255e383a77f6c6a601e4c27659852Safety & 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 install 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. Download a fresh installer 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 Modrinth App_0.21.5_x64-setup.exe safe, or is it malware?
What is Modrinth App_0.21.5_x64-setup.exe?
How many antivirus engines detected Modrinth App_0.21.5_x64-setup.exe?
What should I do if I already installed Modrinth App_0.21.5_x64-setup.exe?
How do I remove Modrinth App_0.21.5_x64-setup.exe?
Is Modrinth App_0.21.5_x64-setup.exe digitally signed?
What is the SHA-256 hash of Modrinth App_0.21.5_x64-setup.exe?
How up to date is this analysis of Modrinth App_0.21.5_x64-setup.exe?
Community
Member reviews and reports for this exact file hash.