Is Terraria.exe safe?
Only TrellixENS flagged the unsigned executable, but one sandbox mapped four offensive techniques, including process injection and impairment of defenses.
The engine result is weak: only 1 of 75 engines flagged the file, no tier-1 engine agreed, and no malware family was established. However, the unsigned executable generated T1055, T1560.002, T1562.001, and T1620 mappings in one sandbox, so its origin should be verified before execution.
960a03bff6050cf7be…5a50dd9e6ba2f3Recommended 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 engine result is weak: only 1 of 75 engines flagged the file, no tier-1 engine agreed, and no malware family was established. However, the unsigned executable generated T1055, T1560.002, T1562.001, and T1620 mappings in one sandbox, so its origin should be verified before execution.
TrellixENS was the only engine among 75 to flag the sample, using the generic Artemis label, while 15 tier-1 engines reported no detection. That isolated result has a substantial false-positive possibility and establishes no named family. A completed sandbox nevertheless mapped process injection, archive collection, defense impairment, and reflective code loading, although it produced no malicious sandbox verdict. Both observed domains were covered by the host-reputation check and had no cached malicious or suspicious classification, while no hashed child files or persistence indicators were recorded. Because the executable is unsigned and the runtime mappings are concerning, the evidence remains mixed rather than clearly benign.
What We Detected
Only 1 of 75 antivirus engines flagged the file. TrellixENS used the generic label Artemis!890F5654041F, while engines.tier1Malicious=0 and 15 tier-1 engines reported no detection. No named malware family was established, and MalwareBazaar and YARAify supplied no corroborating hit.
Threat Behavior
One completed sandbox run mapped T1055 process injection, T1560.002 archive collection, T1562.001 impairment of defenses, and T1620 reflective code loading. These mappings are meaningful risk indicators, but the sandbox did not issue a malicious verdict and the evidence does not prove the exact implementation or intent. The two observed domains were fully covered by the saved host-reputation check, with neither listed as malicious or suspicious; no hashed child files or persistence indicators were recorded.
What To Do Now
Verify that the SHA-256 hash 960a03bff6050cf7be16dfc1a7b19e10fc2c4f8f835a6a3b135a50dd9e6ba2f3 matches a copy obtained from the official game platform. Keep endpoint protection enabled, and avoid running this copy if it came from a crack, mod bundle, mirror, or unsolicited archive.
Where this verdict could be wrong3 caveats
- Fifteen tier-1 engines reported no detection, and the only detection was TrellixENS's generic Artemis label.
- The completed sandbox did not issue a malicious verdict, dropped no hashed child files, and created no listed persistence indicators.
- The unsigned executable produced four offensive-technique mappings, including T1055 and T1562.001, which prevent treating the isolated engine alert as clearly benign.
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 75 engines reported a detection
- No tier-1 engine detected the sample
- No malicious sandbox verdict or persistence indicator was recorded
- Both observed hosts were inspected with no malicious or suspicious cache hits
- No packing, high-entropy code, malicious child, or external-intelligence hit was found
- Unsigned Win32 executable with no verified publisher identity
- Sandbox mapped T1055 process injection
- Sandbox mapped T1562.001 impairment of defenses
- Sandbox mapped T1620 reflective code loading
- TrellixENS reported the generic Artemis!890F5654041F detection
Use only a copy installed or verified through the official game platform, and compare its SHA-256 before launching. Keep endpoint protection enabled and quarantine this copy if its source cannot be authenticated.
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
Complete2 contacted hosts were cross-checked.
YARA
Complete1 signature or behavior rule 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
- 24MITRE ATT&CK techniques
- 4spawned processes
- 2network contacts
- 17filesystem & 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: Attempted to impair or bypass security controls.
High concern: Manipulated how the operating system loads code, which can redirect execution.
High concern: Loaded code directly into memory instead of from a normal file.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
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
Terraria.exe
960a03bff6050cf7be16dfc1a7b19e10fc2c4f8f835a6a3b135a50dd9e6ba2f3
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Terraria.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\SysWOW64\WerFault.exe -u -p 2608 -s 1104
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
04Isolated runtime analysis - Written fileObserved
856ff5e2-418a-4524-92fd-654c489b65ca
C:\ProgramData\Microsoft\Windows\WER\Temp\856ff5e2-418a-4524-92fd-654c489b65ca
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
nexusrules.officeapps.live.com
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
assets.msn.com
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.
- nexusrules.officeapps.live.com
- assets.msn.com
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\PermissionsCheckTestKey
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\terraria.exe|e3561b6f3e4d9ea1
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\terraria.exe|e3561b6f3e4d9ea1\ProgramId
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\terraria.exe|e3561b6f3e4d9ea1\FileId
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\terraria.exe|e3561b6f3e4d9ea1\LowerCaseLongPath
- \REGISTRY\A\{0da4fa1f-9bab-ed4a-c114-fedd6a1296ca}\Root\InventoryApplicationFile\terraria.exe|e3561b6f3e4d9ea1\Name
- C:\ProgramData\Microsoft\Windows\WER\Temp
- C:\ProgramData\Microsoft\Windows\WER\Temp\856ff5e2-418a-4524-92fd-654c489b65ca
- C:\ProgramData\Microsoft\Windows\WER\ReportQueue
- C:\ProgramData\Microsoft\Windows\WER\Temp\32276c1e-3344-45c6-88de-fdef8b98e6cc
- C:\ProgramData\Microsoft\Windows\WER\ReportArchive
- \Sessions\1\BaseNamedObjects\Local\WERReportingForProcess6688
- \Sessions\1\BaseNamedObjects\InventorySynchronizationInventoryApplicationFileMutex3956
- \Sessions\1\BaseNamedObjects\Global\8b3464e3-f05e-4d7b-afba-a5461e6d146d
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
- 1 / 75engines flagged
- 475sources 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
1 of 75 antivirus engines flagged the file, including TrellixENS.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 578 times from 475 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Terraria.exe — 960a03bff6050cf7be16dfc1a7b19e10fc2c4f8f835a6a3b135a50dd9e6ba2f3
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Terraria.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\SysWOW64\WerFault.exe -u -p 2608 -s 1104
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: Temp — C:\ProgramData\Microsoft\Windows\WER\Temp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 856ff5e2-418a-4524-92fd-654c489b65ca — C:\ProgramData\Microsoft\Windows\WER\Temp\856ff5e2-418a-4524-92fd-654c489b65ca
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: nexusrules.officeapps.live.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: assets.msn.com — 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
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\Terraria.exe"
1 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Terraria.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 25.4 MB
- Last analyzed
- Oct 6, 2026, 4:59 PM UTC
960a03bff6050cf7be16dfc1a7b19e10fc2c4f8f835a6a3b135a50dd9e6ba2f3Safety & 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 Terraria.exe safe, or is it malware?
What is Terraria.exe?
How many antivirus engines detected Terraria.exe?
What should I do if I already ran Terraria.exe?
How do I remove Terraria.exe?
What is the SHA-256 hash of Terraria.exe?
How up to date is this analysis of Terraria.exe?
Community
Member reviews and reports for this exact file hash.