Is LobotomyCorp.exe safe?
No engine detected a threat, and the long-established, widely submitted executable showed no offensive behavior, packing, persistence, or disreputable network contacts.
All 75 antivirus engines avoided flagging this executable, including 17 tier-1 engines. It has circulated broadly since 2021, and the completed sandbox run found no offensive techniques, malicious verdict, persistence, dropped payloads, or suspect domains, although the executable is unsigned.
4965e5c565a07ca80a…8ea56371786d91Recommended 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.
All 75 antivirus engines avoided flagging this executable, including 17 tier-1 engines. It has circulated broadly since 2021, and the completed sandbox run found no offensive techniques, malicious verdict, persistence, dropped payloads, or suspect domains, although the executable is unsigned.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including all 17 reporting tier-1 products. The file is also well established, with 1,427 sources and 1,615 submissions since December 2021. One completed sandbox run recorded only ambient techniques and produced no malicious assessment, persistence indicators, written files, or dropped hashes. Reputation checks covered every observed domain and found none categorized as malicious or suspicious. Static inspection found no packer, high-entropy code, or brand mismatch. The lack of a digital signature and one conflicting community annotation are cautions, but they are substantially outweighed by the independent evidence.
What We Detected
None of the 75 antivirus engines flagged the executable, and all 17 reporting tier-1 engines returned it as undetected. The sample has been known since December 2021 and has accumulated 1,615 submissions from 1,427 sources, indicating established circulation rather than a newly introduced file.
Threat Behavior
One completed sandbox run found no offensive-only techniques or malicious sandbox assessment. It recorded no persistence indicators, files written, or dropped hashes. The six observed domains were all covered by the host-reputation check, with none categorized as malicious or suspicious. Static analysis also found no packer, high-entropy code, or brand mismatch.
What To Do Now
The available evidence supports normal use if this executable came from the expected game installation or another source you trust. Because it is unsigned, retain endpoint protection and obtain a fresh copy from the official distributor if the file appeared unexpectedly or differs from the expected installation.
Where this verdict could be wrong3 caveats
- signing.applicable=true but signing.signed=false, so publisher identity cannot be authenticated.
- One communityComments entry reports an automated suspicious assessment with anti-VM and packing tags, although another assessment is informational and current peAnalysis.likelyPacked=false.
- The runtime recorded ambient techniques including T1027, T1071, and T1574.002, but behaviour.offensiveCount=0 and the completed sandbox produced no malicious verdict.
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 engines reported a malicious or suspicious result.
- All 17 reporting tier-1 engines returned undetected.
- The file has 1,427 unique sources and 1,615 submissions dating to 2021.
- The completed sandbox produced no malicious verdict, offensive techniques, persistence, or dropped payloads.
- All 6 contacted domains were inspected, with 0 malicious and 0 suspicious classifications.
- signing.signed=false, so the executable has no authenticated publisher identity.
- communityComments[0] contains a conflicting automated suspicious assessment mentioning anti-VM behavior and packing.
- behaviour.mitreTechniques includes ambient entries T1027, T1071, and T1574.002.
Use it only when it came from the expected game installation or an official distributor. Keep endpoint protection enabled and replace the file with an official copy if its origin is uncertain.
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
Partial6 of 26 contacted hosts were cross-checked; coverage is incomplete.
YARA
CompleteRule evaluation completed with no recorded matches.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 6MITRE ATT&CK techniques
- 13spawned processes
- 26network contacts
- 15filesystem & mutex artifacts
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.
- query.prod.cms.rt.microsoft.com
- www.microsoft.com
- res.public.onecdn.static.microsoft
- fp2e7a.wpc.phicdn.net
- fp2E7A.wpc.2BE4.phicdn.net
- arc.msn.com
- 20.80.129.13
- 20.99.184.37
- 13.107.4.50
- 192.168.0.1
- a83f:8110:5b3:d201:aded:9d5:b325:d901
- 23.216.147.64
- a83f:8110:0:10:101:0:0:5
- 20.99.133.109
- 23.216.147.76
- 192.229.211.108
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERE9D3.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB0B.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB6A.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF250.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERF260.tmp.csv
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 1,427sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,427 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: LobotomyCorp.exe — 4965e5c565a07ca80ad0f3de21568c3e048f4425fcecd99b458ea56371786d91
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — %SAMPLEPATH%\LobotomyCorp.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\4965e5c565a07ca80ad0f3de21568c3e048f4425fcecd99b458ea56371786d91.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: query.prod.cms.rt.microsoft.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
YARA rules
No matchesThe rule pass completed without a saved public match.
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
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
- LobotomyCorp.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 635.5 KB
- Last analyzed
- Oct 4, 2026, 7:15 AM UTC
4965e5c565a07ca80ad0f3de21568c3e048f4425fcecd99b458ea56371786d91Safety & 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 LobotomyCorp.exe safe?
What is LobotomyCorp.exe?
How many antivirus engines detected LobotomyCorp.exe?
What is the SHA-256 hash of LobotomyCorp.exe?
Is it safe to run LobotomyCorp.exe?
How up to date is this analysis of LobotomyCorp.exe?
Community
Member reviews and reports for this exact file hash.