Is UR.exe safe?
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
9fe5fb74600e204a47…a8e5010f9bc3d4Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
Why this file is confirmed malware
The conclusion below is grounded in the recorded hash match and scan evidence.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system. MalwareBazaar is a researcher-curated malware repository; hits there are ground-truth positives.
What We Detected
This file is confirmed confirmed malware — abuse.ch researchers uploaded this exact sample to MalwareBazaar as known malware. Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system.
Threat Behavior
Refer to the confirmed malware threat family for known tactics.
What To Do Now
Delete this file from the device, then empty the Recycle Bin or Trash. Scan your system with an up-to-date antivirus.
Where this verdict could be wrong1 caveat
- If this hash is a polymorphic-collision with a legitimate build, the MB label would be misleading — but MB curation makes this extremely rare.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- MalwareBazaar confirmed family: confirmed malware
- Researcher-uploaded malware sample
Delete this file from the device, then empty the Recycle Bin or Trash. Run a full-system antivirus scan.
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
Partial3 of 23 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete8 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
- 21MITRE ATT&CK techniques
- 15spawned processes
- 23network contacts
- 22filesystem & 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: Used an input-capture technique that can record credentials or keystrokes.
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: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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.
Threat context
How trojans work
A trojan disguises itself as something useful or harmless to trick you into running it. Once open, it does its real job in the background — anything from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
UR.exe
9fe5fb74600e204a4739a0ed262f16ab6c7eb9f970f61d6315a8e5010f9bc3d4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\services.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
iconcache_16.db
C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_16.db
04Isolated runtime analysis - Written fileObserved
Download-1.tmp
C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
06Contacted-host cross-check - Contacted hostDerived
res.public.onecdn.static.microsoft
Saved reputation verdict: safe.
07Contacted-host cross-check - +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; 1 returned "malicious".
Adversary techniques mapped to the MITRE ATT&CK framework.
- www.microsoft.com
- res.public.onecdn.static.microsoft
- svc.ha-teams.office.com
- a83f:8110:3151:75ff:3050:74ff:2f4f:73ff
- 192.168.0.15
- 20.99.186.246
- 20.99.133.109
- 23.216.81.152
- 23.209.30.16
- 20.99.185.48
- 192.168.0.32
- 192.168.0.88
- 192.168.0.63
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryApplication\0000c34c48b48a14753d8877e705591744db00000000\Publisher
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryDevicePnp\acpi/genuineintel_-_intel64_family_6_model_79_-____________intel(r)_xeon(r)_cpu_@_2.20ghz/_0\DriverVerVersion
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryDevicePnp\acpi/genuineintel_-_intel64_family_6_model_79_-____________intel(r)_xeon(r)_cpu_@_2.20ghz/_1\DriverVerVersion
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryDevicePnp\acpi/pnp0303/4&2c352a27&0\DriverVerVersion
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryDevicePnp\acpi/pnp0700/4&2c352a27&0\DriverVerVersion
- \REGISTRY\A\{81E1BB84-5581-F5B6-CF30-9DF4D1ECB235}\Root\InventoryDevicePnp\acpi/pnp0a03/0\DriverVerVersion
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_16.db
- C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
- C:\Windows\System32\Tasks\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer\thumbcache_32.db
- C:\Users\user\AppData\Local\Microsoft\Windows\Explorer\thumbcache_idx.db
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
- Local\Shell.CMruPidlList
- Local\MSCTF.Asm.MutexDefault1
- DefaultTabtip-MainUI
- Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:thumbcache_idx.db!rwWriterMutex
- Global\C::Users:user:AppData:Local:Microsoft:Windows:Explorer:thumbcache_32.db!dfMaintainer
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 75748ac68f18ffbfb1fe…2c720aNever scannednever seen before
- 31a213590b2ac130e390…d459f9Never 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.
- 8rule hits recorded
- 1 / 75engines flagged
- 3,664sources 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 appears in a researcher-curated malware database.
Verdict inputView chapterProvenanceObservedSourceResearcher malware databaseObserved at - 02
1 isolated runtime environment classified the observed behavior as malicious.
Verdict inputView chapterProvenanceObservedSourceIsolated runtime analysisObserved at - 03
7 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 04
Scanned file: UR.exe — 9fe5fb74600e204a4739a0ed262f16ab6c7eb9f970f61d6315a8e5010f9bc3d4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: iconcache_16.db — C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_16.db
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: Download-1.tmp — C:\Windows\ServiceProfiles\LocalService\AppData\Local\FontCache\Fonts\Download-1.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 10
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
Category: generic-trojan
One or more independent reference databases matched 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.
- BobSoftMiniDelphiBoBBobSoft
- Borland
- DebuggerCheck__API
- HUNTING_SUSP_TLS_SECTION
- pe_detect_tls_callbacks
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\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.exeUnsigned, packed PE with sandbox-observed network activity. The packing step hides the payload until execution; the network call fetches / reports for the next stage. Classic dropper / stager behaviour.
Evidencewww.microsoft.com
1 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
A known packer signature (UPX / Themida / VMProtect / etc.) matched this file. Packers aren't malicious on their own, but most malware uses them.
Packers compress or encrypt the executable and only unpack it at runtime. Legitimate commercial software uses them too — but if the file is also unsigned and rare, it's a strong malware signal.
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
- UR.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 3.2 MB
- Last analyzed
- Sep 25, 2026, 2:13 AM UTC
9fe5fb74600e204a4739a0ed262f16ab6c7eb9f970f61d6315a8e5010f9bc3d4Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is UR.exe a virus?
What is UR.exe?
How many antivirus engines detected UR.exe?
What should I do if I already ran UR.exe?
How do I remove UR.exe?
What kind of malware is UR.exe?
Has UR.exe been seen before?
What is the SHA-256 hash of UR.exe?
How up to date is this analysis of UR.exe?
Community
Member reviews and reports for this exact file hash.