Is TekkenScript.exe safe?
Eight of 75 engines flagged this packed executable, including one tier-1 PUA detection, while its signature trust and observed IP reputation remain unresolved.
The executable combines packing, eight antivirus detections, and an observed direct-IP connection with an unverified publisher identity. However, only one tier-1 engine detected it, the sandbox recorded no offensive-only behavior, and the dominant specific label describes potentially unwanted software rather than a confirmed trojan family.
9503e8ca5f0b325379…924aafa024fc75Recommended 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 executable combines packing, eight antivirus detections, and an observed direct-IP connection with an unverified publisher identity. However, only one tier-1 engine detected it, the sandbox recorded no offensive-only behavior, and the dominant specific label describes potentially unwanted software rather than a confirmed trojan family.
Eight of 75 engines detected the sample, but Microsoft was the only tier-1 detector and labeled it PUA:Win32/Creprote. Other detections include grayware and generic machine-learning labels, so there is no strong family consensus. The executable contains high-entropy UPX-style sections, making its code harder to inspect and adding risk. One sandbox run observed a connection to 162.159.36.2 but produced no malicious sandbox verdict, dropped payload, persistence indicator, or offensive-only technique. Because the publisher is not trusted, signature verification is unresolved, and no complete host-reputation check is available, the evidence does not support treating the file as established benign software.
What We Detected
Eight of 75 antivirus engines flagged the executable. Microsoft reported PUA:Win32/Creprote, CrowdStrike reported grayware, and several other engines used generic or certificate-related labels; only one tier-1 engine detected it, so there is no strong independent family consensus.
Threat Behavior
The executable is likely packed, with the UPX1 section reaching entropy 7.93. A completed sandbox run observed contact with 162.159.36.2 and ambient techniques including T1027, T1027.002, T1071, and T1129, but it recorded no offensive-only techniques, malicious sandbox verdict, dropped files, or persistence. No complete reputation result is available for the contacted IP.
What To Do Now
Do not run the file on a primary system unless its origin and publisher can be independently verified. Keep endpoint protection enabled, obtain a fresh copy from the developer's official release channel, and use an isolated environment if further examination is necessary.
Where this verdict could be wrong4 caveats
- Only 1 of 17 tier-1 engines flagged the sample; 16 tier-1 engines reported no detection.
- The completed sandbox produced no malicious verdict, no offensive-only techniques, and no recorded dropped files or persistence indicators.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false, although absent matches do not establish benignity.
- Microsoft and CrowdStrike categorize the detection as PUA or grayware rather than a confirmed trojan family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 16 of 17 tier-1 engines reported no detection
- No malicious sandbox verdict across one completed run
- No offensive-only MITRE techniques were observed
- No dropped files or persistence indicators were recorded
- No MalwareBazaar, CIRCL, or YARAify match was found
- 8/75 antivirus detections
- Microsoft PUA:Win32/Creprote detection
- Likely packed executable with UPX1 entropy of 7.93
- Observed connection to 162.159.36.2 without a completed reputation cross-check
- Publisher is not on the trusted list and has no signer history
- Signature verification status is unresolved
Avoid executing this copy until the publisher and download source are independently verified. Keep security protection enabled and replace it with a copy obtained through the developer's official channel.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete8 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete3 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
- 4MITRE ATT&CK techniques
- 1spawned processes
- 1network contacts
- 0filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
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
TekkenScript.exe
9503e8ca5f0b325379930516cd95f141bc3964b2b23f608703924aafa024fc75
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\user\Desktop\tekkenscript.exe"
02Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
03Isolated runtime analysis
3 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.
- 162.159.36.2
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 3rule hits recorded
- 8 / 75engines flagged
- 17sources 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
8 of 75 antivirus engines flagged the file, including Bkav and CrowdStrike.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 19 times from 17 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: TekkenScript.exe — 9503e8ca5f0b325379930516cd95f141bc3964b2b23f608703924aafa024fc75
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\user\Desktop\tekkenscript.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: pua
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.
PE is packed (high-entropy code or known packer) AND unsigned AND at least one engine flagged it. Packing alone is common in legit software; packing + unsigned + signal is the malware-dropper pattern.
Evidencehigh-entropy code sectionThe 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.
Evidence162.159.36.2Unsigned, 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.
Evidence162.159.36.2
8 of 75 engines flagged this file
View all 75 engine results
Section entropy & packers
Executable sections have high entropy (7.2+) — the code is compressed or encrypted and only decrypted at runtime. Classic packing behaviour.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- TekkenScript.exe
- Format
- Win32 EXE
- Code signing
- Signature not verified: 上海明盛网络科技有限公司
- Size
- 920.0 KB
- Last analyzed
- Sep 15, 2026, 2:52 PM UTC
9503e8ca5f0b325379930516cd95f141bc3964b2b23f608703924aafa024fc75Safety & 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 TekkenScript.exe safe, or is it malware?
What is TekkenScript.exe?
How many antivirus engines detected TekkenScript.exe?
What should I do if I already ran TekkenScript.exe?
How do I remove TekkenScript.exe?
What kind of malware is TekkenScript.exe?
Is TekkenScript.exe digitally signed?
What is the SHA-256 hash of TekkenScript.exe?
How up to date is this analysis of TekkenScript.exe?
Community
Member reviews and reports for this exact file hash.