Suspicious
Unsigned rare PE with process-injection and direct-IP behaviour flagged by three tier-2 engines.
2035c328e6ea20abc7…6d4445f72bThe verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
The combination of tier-2 detections, offensive MITRE techniques, and direct-IP C2 without DNS raises concern, yet the complete absence of tier-1 consensus and lack of dropped malicious children or known-bad hosts keeps the file from crossing into a clear malicious verdict. The file's extreme rarity and unsigned status further limit confidence in either direction.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1Malicious=0 and tier1FamilyConsensus.strong=false
behaviour.offensiveTechniques=["T1055","T1134"] and triggeredHeuristics[0].rule="MalwareTips.Synth.ProcessInjection"
signing.verified=false and prevalence.classification="rare_new"
contactedIps=["162.159.36.2"] with zero contactedDomains
similarHashes.length=0 and externalIntel.yaraify.ruleCount=0
- Zero tier-1 engines flagged the sample
- No malicious dropped children or contacted hosts
- No YARAify or CIRCL corroboration
- Unsigned binary with zero prior submissions
- Process injection (T1055) observed in sandbox
- Direct-IP contact bypassing DNS reputation systems
- Three tier-2 engines assigned malicious confidence scores
Treat as suspicious pending additional sandbox or threat-intel results; avoid execution until further confirmation.
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
- \Device\HarddiskVolume2\\__tmp_rar_sfx_access_check_48625
- C:\__tmp_rar_sfx_access_check_48625
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- __tmp_rar_sfx_access_check_224015
- C:\\ETAP 2400
- __tmp_rar_sfx_access_check_224015
- C:\ETAP 2400\LFNRSimu.exe
- C:\__tmp_rar_sfx_access_check_4251468
YARA + heuristic rules that fired
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox 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.exeSample contacted 1 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence162.159.36.2
5 detections across 74 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How often this file shows up in the wild
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- Patch.exe
- Size
- 8.82 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 2035c328e6ea20abc718a83fc339e931e7200f9b31c0e026deedb66d4445f72b
- MD5
- 8f95cca0074835439c80173af36c3c18
- SHA-1
- db0cfc9e0f8f5b1843ecfa632457e5f07f91fcf6
- PE imphash
- 2057790ae7855765d51bdc4142e62f9c
- First seen (VT)
- 7/11/2026, 9:18:48 AM
- Last analysis (VT)
- 7/11/2026, 9:18:48 AM
- First scan (MalwareTips)
- 7/11/2026, 9:37:27 AM
- Last scan (MalwareTips)
- 7/11/2026, 9:37:27 AM
Safety FAQ
Common questions about Patch.exe, answered from the scan data above.
- Patch.exe is suspicious — treat it as unsafe until you're sure. 5 of 74 antivirus engines flag it, which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- Patch.exe is a Windows executable program, about 8.8 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 5 of 74 antivirus engines flagged Patch.exe, 5 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove Patch.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original Patch.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- The SHA-256 hash of Patch.exe is 2035c328e6ea20abc718a83fc339e931e7200f9b31c0e026deedb66d4445f72b, and its MD5 is 8f95cca0074835439c80173af36c3c18. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 11, 2026. Because a file's hash never changes, the identity of Patch.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.