Is TheoTown.exe safe?
Seventeen of 76 engines flagged this unsigned executable, including four tier-1 detections, while observed T1055 activity adds concern despite conflicting family labels.
The unsigned executable drew 17 detections from 76 engines, including four tier-1 products, and one sandbox mapped activity to T1055 process injection. However, the detections lack family consensus, the completed sandbox did not issue a malicious conclusion, and both observed no complete contacted-host reputation result was available cache results, leaving materially mixed evidence.
90bf21d0760f9243d4…ee91e1b1b07b7eRecommended 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.
The unsigned executable drew 17 detections from 76 engines, including four tier-1 products, and one sandbox mapped activity to T1055 process injection. However, the detections lack family consensus, the completed sandbox did not issue a malicious conclusion, and both observed no complete contacted-host reputation result was available cache results, leaving materially mixed evidence.
Four tier-1 products were among the 17 of 76 engines that flagged the executable, which is too substantial to treat as routine heuristic noise. Their labels conflict, ranging from a generic Trojan and Artemis heuristic to PUA, so no specific family attribution is reliable. One completed sandbox run mapped activity to T1055 process injection, but it did not produce a malicious sandbox conclusion or record persistence and dropped files. The executable is unsigned and has no signer history, removing an important source of publisher assurance. Its established prevalence, unpacked-looking code, and complete non-malicious cache results for both observed domains are counter-signals, but they do not outweigh the combined engine and injection concerns enough to recommend normal execution.
What We Detected
Seventeen of 76 antivirus engines flagged the executable. Four tier-1 products participated: Fortinet reported PossibleThreat, Ikarus reported Agent, McAfee reported Artemis, and Sophos reported a generic machine-learning PUA label. These labels do not converge on a specific family, but their number and quality make a simple low-trust false positive explanation unlikely.
Threat Behavior
One completed sandbox run mapped activity to MITRE T1055, which is associated with process injection. The mapping supports concern but does not identify the exact injection method or prove intent. The run did not issue a malicious sandbox conclusion and recorded no persistence indicators, written files, or dropped hashes. Both observed domains were inspected in the host cache and had no malicious or suspicious verdict, although the payload also lists IP contacts that were not represented in that domain-only cross-check.
What To Do Now
Do not run this copy on a production or personal system. Obtain the program from its official distribution channel, compare its SHA-256 hash with a publisher-provided value if available, and keep endpoint protection enabled. If execution is necessary for research, use an isolated disposable environment without sensitive data or credentials.
Where this verdict could be wrong5 caveats
- engines.tier1FamilyConsensus.strong=false; the four tier-1 detections do not agree on a concrete malware family.
- behaviour.hasMaliciousSandboxVerdict=false, with no persistence indicators, written files, or dropped hashes recorded.
- contactedHosts.inspected=2 covers both observed domains; res.public.onecdn.static.microsoft and www.microsoft.com had no cached malicious or suspicious verdict.
- BitDefender, ESET-NOD32, Avast, Avira, DrWeb, and several other tier-1 engines did not detect the sample.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=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.
- Established prevalence: 211 submitters and 254 submissions since 2022
- Completed sandbox did not issue a malicious conclusion
- No dropped hashes, persistence indicators, or written files were recorded
- Both observed no complete contacted-host reputation result was available cache results
- PE analysis found no likely packing or high-entropy code
- 17/76 antivirus detections
- Four tier-1 engines flagged the sample
- Unsigned Win32 executable with no signer history
- Runtime evidence mapped to MITRE T1055 process injection
- No strong agreement on a named family, suggesting uncertain attribution
Quarantine this copy and replace it with a fresh download from the official publisher channel. Keep endpoint protection enabled, and only investigate further in an isolated disposable environment.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete17 of 76 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 of 22 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
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
- 5MITRE ATT&CK techniques
- 6spawned processes
- 22network contacts
- 15filesystem & 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.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Note: Collects details about your system.
Note: Loads extra code modules 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
TheoTown.exe
90bf21d0760f9243d4475c366159f51eb4f64973e3e4a4c680ee91e1b1b07b7e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
javaw -jar TheoTown66.lby b0c1116b7cae1e988007a54718e15126
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostDerived
res.public.onecdn.static.microsoft
Saved reputation verdict: safe.
04Contacted-host cross-check - Contacted hostDerived
www.microsoft.com
Saved reputation verdict: safe.
05Contacted-host cross-check - +1 more recorded observation in Analyst mode
5 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.
- res.public.onecdn.static.microsoft
- www.microsoft.com
- 192.168.0.11
- 23.216.147.64
- 20.99.184.37
- 192.229.211.108
- 20.99.185.48
- 23.216.147.76
- 20.99.186.246
- 20.96.52.198
- 152.195.19.97
- a83f:8110:87c1:ffff:3033:eaea:87c1:ffff
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER951.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERA1D.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WERA5C.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E0.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER28E2.tmp.csv
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 17 / 76engines flagged
- 211sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
17 of 76 antivirus engines flagged the file, including Antiy-AVL and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 211 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 04
Scanned file: TheoTown.exe — 90bf21d0760f9243d4475c366159f51eb4f64973e3e4a4c680ee91e1b1b07b7e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — javaw -jar TheoTown66.lby b0c1116b7cae1e988007a54718e15126
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: res.public.onecdn.static.microsoft — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at - 08
Contacted host: www.microsoft.com — Saved reputation verdict: safe.
ProvenanceDerivedSourceContacted-host cross-checkObserved at
Detection sources at a glance
Category: generic-trojan
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
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>\Desktop\file.exe"
17 of 76 engines flagged this file
View all 76 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
- TheoTown.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 303.5 KB
- Last analyzed
- Oct 4, 2026, 7:28 PM UTC
90bf21d0760f9243d4475c366159f51eb4f64973e3e4a4c680ee91e1b1b07b7eSafety & 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 TheoTown.exe safe, or is it malware?
What is TheoTown.exe?
How many antivirus engines detected TheoTown.exe?
I already downloaded and ran TheoTown.exe — what should I do?
How do I remove TheoTown.exe?
What kind of malware is TheoTown.exe?
What is the SHA-256 hash of TheoTown.exe?
How up to date is this analysis of TheoTown.exe?
Community
Member reviews and reports for this exact file hash.