Is osu.pilot.exe safe?
Only Bkav flagged this unsigned executable, but one sandbox exposed LSASS-related activity and unresolved direct-IP traffic that warrant caution.
Only 1 of 74 engines detected the file, and that result came from low-trust Bkav while all 17 tier-1 engines were silent. However, the unsigned executable produced LSASS-related and direct-IP indicators in one sandbox, and the two contacted IP addresses were not reputation-checked completely.
9488c7937dc9874501…806c160b5374deRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy 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.
Only 1 of 74 engines detected the file, and that result came from low-trust Bkav while all 17 tier-1 engines were silent. However, the unsigned executable produced LSASS-related and direct-IP indicators in one sandbox, and the two contacted IP addresses were not reputation-checked completely.
The antivirus pattern strongly favors a false positive: Bkav alone flagged the sample, while all 17 reporting tier-1 engines left it undetected. The file is also established rather than newly observed, with 126 sources and 137 submissions over 397 days. Countering that, one completed sandbox exposed an LSASS-related heuristic, T1486, and direct connections to two IP addresses. No sandbox issued a malicious verdict and none of the 10 inspected children was identified as malicious, but host-reputation coverage for those IPs is unavailable. The lack of a verified signature and the unresolved runtime indicators justify caution rather than treating the isolated engine result as conclusively benign.
What We Detected
Bkav was the only engine to flag the file, reporting W32.Malware.E2D23101. That is 1 of 74 engines, with no tier-1 detections or family consensus; Microsoft, Kaspersky, BitDefender, ESET-NOD32, Avast, and the other reporting tier-1 engines remained silent. The executable has no verified code signature, although it has been submitted 137 times by 126 sources over 397 days.
Threat Behavior
One sandbox run surfaced an LSASS-related heuristic, technique T1486, and direct traffic to 20.99.133.109 and 217.20.54.37. The sandbox did not issue a malicious verdict, and none of 10 inspected child files was identified as malicious. No complete host-reputation result is available for the observed IP addresses, so their risk remains unresolved. Two prior files sharing the imphash received cautious assessments, but those were imphash-only matches without signer correlation and therefore provide limited support.
What To Do Now
Keep endpoint protection enabled and verify the download against the developer's official release channel or a publisher-provided checksum. If the source cannot be verified, avoid running the file on a production or personal system until the contacted IP addresses and LSASS-related activity are independently explained.
Where this verdict could be wrong4 caveats
- All 17 reporting tier-1 engines, including Microsoft, Kaspersky, BitDefender, ESET-NOD32, and Avast, left the file undetected.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false across 10 inspected children.
- The executable is unsigned, so there is no verified publisher identity to support the low-detection interpretation.
- The single sandbox surfaced LSASS-related and direct-IP indicators, and complete host-reputation coverage is unavailable.
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 1 of 74 engines detected the file
- tier1Malicious=0 and all 17 reporting tier-1 engines were silent
- The only detection came from low-trust Bkav
- No completed sandbox issued a malicious verdict
- No malicious child was found among 10 inspected children
- Unsigned Win32 executable with no verified publisher identity
- Sandbox surfaced LSASS-related process activity
- T1486 appeared among the observed MITRE techniques
- Direct connections were made to 20.99.133.109 and 217.20.54.37
- No complete reputation result is available for the contacted IP addresses
- Two imphash-only precedents received cautious assessments
Keep security protection enabled and obtain the executable only from a verified official source. Do not run it on a sensitive system unless its checksum and network destinations can be independently validated.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 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
- 17MITRE ATT&CK techniques
- 15spawned processes
- 2network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
Moderate concern: Decoded or unpacked concealed content while running.
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
osu.pilot.exe
9488c7937dc987450106656e817e36e40295e2a7b0a7e2bc68806c160b5374de
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\osu.pilot.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imaging.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imagingcms.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingcms.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
20.99.133.109
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
217.20.54.37
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.
- 20.99.133.109
- 217.20.54.37
- C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingft.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingtk.cp312-win_amd64.pyd
- \Sessions\1\BaseNamedObjects\Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 76bba42b1392dc57a867…a36e8dNever scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 741859cf238c3a63bbb2…561c2eNever scannednever seen before
- 1947f8b188ab4ab6aa72…368fb7Never scannednever seen before
- c15ab85438728bf2c60d…3acdf4Never scannednever seen before
- 8924545cc92584169138…3f3610Never scannednever seen before
- d134e731716bb4538596…d3f5e2Never scannednever seen before
- e64fd2e639da6f654d9b…82eb0aNever scannednever seen before
- 517204ee436d08efc287…ad772cNever scannednever seen before
- b6cd5c6f2b54d8914267…303cdcNever 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
- 1 / 74engines flagged
- 126sources 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 74 antivirus engines flagged the file, including Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 126 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 137 times from 126 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: osu.pilot.exe — 9488c7937dc987450106656e817e36e40295e2a7b0a7e2bc68806c160b5374de
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\osu.pilot.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imagingcms.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI28442\PIL\_imagingcms.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 217.20.54.37 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
Sandbox 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.exeThe 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.
Evidence20.99.133.109 · 217.20.54.37
1 of 74 engines flagged this file
View all 74 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
- osu.pilot.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 61.8 MB
- Last analyzed
- Sep 19, 2026, 10:59 AM UTC
9488c7937dc987450106656e817e36e40295e2a7b0a7e2bc68806c160b5374deSafety & 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 run 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. Get a fresh copy 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 osu.pilot.exe safe, or is it malware?
What is osu.pilot.exe?
How many antivirus engines detected osu.pilot.exe?
I already downloaded and ran osu.pilot.exe — what should I do?
How do I remove osu.pilot.exe?
What is the SHA-256 hash of osu.pilot.exe?
How up to date is this analysis of osu.pilot.exe?
Community
Member reviews and reports for this exact file hash.