Is MailRanger.exe safe?
Only 2 of 75 engines flagged this established file, both low-trust, while tier-one engines and independent intelligence supplied no malware-family corroboration.
The two detections are generic low-trust alerts, with no tier-one engine identifying malware and no named family consensus. One sandbox recorded potentially offensive techniques and direct-IP traffic, but issued no malicious verdict, and a complete reputation check for those IP addresses is unavailable.
090a400f85935543d2…dcc695184c9ed6Recommended 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.
The two detections are generic low-trust alerts, with no tier-one engine identifying malware and no named family consensus. One sandbox recorded potentially offensive techniques and direct-IP traffic, but issued no malicious verdict, and a complete reputation check for those IP addresses is unavailable.
Cylance and Trapmine are the only detectors among 75 engines, and both are categorized as low-trust. No tier-one engine flagged the sample, and the detections provide generic labels rather than a recognized malware family. The file has also circulated broadly since 2019, with 440 sources and 497 submissions. Runtime evidence mapped activity to process injection and other offensive techniques, but the completed sandbox did not issue a malicious verdict. Because the contacted-IP reputation check was not completed or saved, those network contacts remain an unresolved limitation rather than evidence of benign traffic.
What We Detected
Two of 75 antivirus engines flagged the executable: Cylance reported “Unsafe,” while Trapmine produced a low-confidence machine-learning alert. Both are low-trust detections, and no tier-one engine identified malware or agreed on a threat family. The file has been observed since 2019 across 440 sources and 497 submissions, which reduces concern that it is a newly introduced, obscure payload.
Threat Behavior
One completed sandbox run mapped activity to T1055 process injection, T1134 token manipulation, T1486 data encryption for impact, and T1560 archive collection. These mappings can be security-relevant, but the sandbox itself did not produce a malicious verdict. Direct-IP communications were also observed; however, contactedHosts is unavailable, so no complete reputation conclusion can be drawn about those addresses. Ten dropped components were inspected without a malicious-child finding, although their individual verdicts remain unknown.
What To Do Now
Obtain the executable from its original, trusted distribution channel and verify its SHA-256 value before running it. Keep endpoint protection enabled, and use an isolated environment if the source or expected purpose cannot be confirmed.
Where this verdict could be wrong3 caveats
- The executable is unsigned (signing.signed=false), so publisher identity and provenance cannot be authenticated.
- One sandbox mapped activity to T1055 process injection and observed direct-IP traffic; contactedHosts=null leaves those IP addresses without a complete reputation result.
- The ten dropped children have unknown individual verdicts even though droppedChildren.hasMaliciousChild=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 2/75 engines flagged the sample, both low-trust
- engines.tier1Malicious=0 with 16 tier-one engines reporting clean
- Established prevalence: 440 sources and 497 submissions since 2019
- behaviour.hasMaliciousSandboxVerdict=false
- No malicious dropped child or external-intelligence hit
- Unsigned Win32 executable with no authenticated publisher
- T1055 process-injection mapping in one sandbox
- Five offensive MITRE technique mappings
- Direct-IP traffic without a completed host-reputation check
- Ten dropped children have unknown individual verdicts
Use only a copy obtained from a trusted original source and confirm the SHA-256 hash. Keep endpoint protection enabled and isolate execution if provenance cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were observed without a completed reputation cross-check.
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
- 26MITRE ATT&CK techniques
- 7spawned processes
- 20network contacts
- 40filesystem & 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
MailRanger.exe
090a400f85935543d2d2097e88d4c82c11be639d5684a32829dcc695184c9ed6
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
${SamplePath}\090a400f85935543d2d2097e88d4c82c11be639d5684a32829dcc695184c9ed6.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_ARC4.cp37-win32.pyd
C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_ARC4.cp37-win32.pyd
04Isolated runtime analysis - Written fileObserved
_Salsa20.cp37-win32.pyd
C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_Salsa20.cp37-win32.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
204.79.197.203
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
104.69.90.31
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.
- 204.79.197.203
- 104.69.90.31
- 23.216.147.76
- a83f:8110:0:0:700:700:2800:4000
- 13.107.4.50
- 23.216.147.64
- 20.80.129.13
- 52.251.79.25
- 20.99.132.105
- 20.99.184.37
- C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_ARC4.cp37-win32.pyd
- C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_Salsa20.cp37-win32.pyd
- C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_chacha20.cp37-win32.pyd
- C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_raw_aes.cp37-win32.pyd
- C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_raw_aesni.cp37-win32.pyd
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER194F.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1961.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1971.tmp.txt
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- \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
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 938aa026602672582444…816623Never scannednever seen before
- 028786db35b2a3a0096f…1cb1c7Never scannednever seen before
- c66d5f9ea5f14bc3259f…1a30e2Never scannednever seen before
- f56b749c01cc82118ffe…e7b095Never scannednever seen before
- 26f7fc8987022f6f095e…b169f2Never scannednever seen before
- 2257ce4a8f4541d89a6b…63ce26Never scannednever seen before
- e36d5bf1bb443fb988f1…b059d8Never scannednever seen before
- 6754fbd887390e489fe9…53f3ceNever scannednever seen before
- 76fcf1d2f2240eb1ca86…418603Never scannednever seen before
- 25ae7577e066fa80519a…14a91dNever 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
- 2 / 75engines flagged
- 440sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash has a long, established submission history across 440 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
2 of 75 antivirus engines flagged the file, including Cylance and Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 04
Scanned file: MailRanger.exe — 090a400f85935543d2d2097e88d4c82c11be639d5684a32829dcc695184c9ed6
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — ${SamplePath}\090a400f85935543d2d2097e88d4c82c11be639d5684a32829dcc695184c9ed6.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _ARC4.cp37-win32.pyd — C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_ARC4.cp37-win32.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _Salsa20.cp37-win32.pyd — C:\Users\Admin\AppData\Local\Temp\_MEI21842\Crypto\Cipher\_Salsa20.cp37-win32.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 204.79.197.203 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 104.69.90.31 — 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.
Evidence"C:\Users\<USER>\AppData\Local\Temp\file.exe"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.
Evidence204.79.197.203 · 104.69.90.31 · 23.216.147.76
2 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- MailRanger.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 39.6 MB
- Last analyzed
- Sep 14, 2026, 10:27 PM UTC
090a400f85935543d2d2097e88d4c82c11be639d5684a32829dcc695184c9ed6Safety & 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 MailRanger.exe safe?
What is MailRanger.exe?
How many antivirus engines detected MailRanger.exe?
What is the SHA-256 hash of MailRanger.exe?
Is it safe to run MailRanger.exe?
How up to date is this analysis of MailRanger.exe?
Community
Member reviews and reports for this exact file hash.