Suspicious
Unsigned PyInstaller-built EXE with direct-IP C2, 8 YARA hits, and 2 tier-1 detections but limited consensus.
16ac9cda936e4d44fe…2e1fa37f52The reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Low tier-1 consensus (only 2 of 17) and absence of named family agreement keep the sample out of clear malicious territory. However, the combination of unsigned status, direct-IP C2 without DNS, T1486 technique, and multiple YARA matches from community researchers creates mixed signals that exceed typical false-positive patterns. Prevalence is high yet reputation remains zero and community tags reference known threat families. No malicious dropped children or sandbox verdicts exist to confirm execution of harmful payloads.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1Malicious=2 (Fortinet, TrendMicro-HouseCall) with tier1FamilyConsensus.family=possiblethreat
behaviour.offensiveTechniques includes T1486 and MalwareTips.Synth.DirectIpC2 fired on 16 direct IPs with zero domains
externalIntel.yaraify.ruleCount=8 including Detect_PyInstaller and botnet_plaintext_c2
signing.verified=false with no signerStats history
communityComments tags reference black-basta, cobalt-strike, luca-stealer
- Majority of tier-1 engines returned undetected
- No malicious dropped children
- No malicious sandbox verdict
- High submission volume (common_old)
- Unsigned executable
- Direct IP contacts without DNS resolution
- YARA rules for PyInstaller and botnet strings
- Offensive MITRE technique T1486
- Community tags referencing ransomware and stealer families
Treat as suspicious pending further sandbox or dynamic analysis; do not run on systems with sensitive data.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Talks to a remote server to take commands or send out your data.
High concern: Encrypts your files and demands payment — ransomware behaviour.
High concern: Hijacks how Windows loads programs so it runs automatically.
Moderate concern: Obfuscates or packs its code to avoid detection.
Moderate concern: Lists running programs — often to find security tools.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Scans through your files and folders.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
tl0101dh26ys corroborated by 3 sources
- 8 YARA rulesbotnet_plaintext_c2, DebuggerCheck__API, DebuggerException__SetConsoleCtrl
- VT (74 engines)tl0101dh26ys
- MT AI Enginepossiblethreat
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.
- 217.20.54.35
- 23.196.145.221
- 104.98.118.146
- 20.69.140.28
- 23.32.75.35
- a83f:8110:0:0:2800:0:0:0
- 192.168.0.42
- 104.98.118.147
- 23.55.140.42
- 192.168.0.28
- C:\Users\<USER>\AppData\Local\Temp\_MEI65842\VCRUNTIME140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI65842\_bz2.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI65842\_decimal.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI65842\_hashlib.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI65842\_lzma.pyd
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 48f4a239c25354f0e9f8…17ecedNever scannednever seen before
- 3271d39d7b4dcd841e8e…efe5e5Never scannednever seen before
- cb71909bf01a3a7a4c73…d46e13Never scannednever seen before
- 98074c85650a420a095a…b084e9Never scannednever seen before
- 81eca6840b87f2def9fc…d7aaaaNever scannednever seen before
- 4f05f31ca026bbfeeee4…7ab5deNever scannednever seen before
- 3130bf26da0c840c1e02…5a3539Never scannednever seen before
- 47576cae321c80e69c7f…ac6b91Never scannednever seen before
- 165be658ab7d61ffc3df…d3acd7Never scannednever seen before
- 76f6bc85fc9cb89bc3f9…5415eaNever scannednever seen before
1 corroborating signal from researcher-curated sources
- botnet_plaintext_c2by cipAttempts to match at least some of the strings used in some botnet variants which use plaintext communication protocols.
- DebuggerCheck__API
- DebuggerException__SetConsoleCtrl
- Detect_PyInstallerby Obscurity Labs LLCDetects PyInstaller compiled executables across platforms
- golang_bin_JCorn_CSC846by Justin CornwellCSC-846 Golang detection ruleset
YARA & heuristic rule matches
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
- botnet_plaintext_c2
- DebuggerCheck__API
- DebuggerException__SetConsoleCtrl
- Detect_PyInstaller
- golang_bin_JCorn_CSC846
Sample contacted 16 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence217.20.54.35 · 23.196.145.221 · 104.98.118.146
7 detections across 74 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked 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.
Forensic fingerprint
- File name
- TIKTOK 60FPS PATCH.exe
- Size
- 9.85 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- 16ac9cda936e4d44fe093b5014db32fc4fe2c6c7166aa4311296b42e1fa37f52
- MD5
- b8a767c8fd97ac1bdfdebb2f629e2387
- SHA-1
- a88648aef4186fc01268fae0c0a60b6bb06f0d08
- PE imphash
- 965e162fe6366ee377aa9bc80bdd5c65
- First seen (VT)
- 5/11/2025, 9:53:26 AM
- Last analysis (VT)
- 7/14/2026, 10:25:27 PM
- First scan (MalwareTips)
- 7/18/2026, 9:29:05 PM
- Last scan (MalwareTips)
- 7/18/2026, 9:29:05 PM
Safety FAQ
Common questions about TIKTOK 60FPS PATCH.exe, answered from the scan data above.
- TIKTOK 60FPS PATCH.exe is suspicious — treat it as unsafe until you're sure. 7 of 74 antivirus engines flag it (family: possiblethreat), which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- TIKTOK 60FPS PATCH.exe is a Windows executable program, about 9.9 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 7 of 74 antivirus engines flagged TIKTOK 60FPS PATCH.exe, 7 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove TIKTOK 60FPS PATCH.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original TIKTOK 60FPS PATCH.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- TIKTOK 60FPS PATCH.exe is classified as a trojan — malware disguised as something harmless to trick you into running it. Engines attribute it to the possiblethreat family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- The SHA-256 hash of TIKTOK 60FPS PATCH.exe is 16ac9cda936e4d44fe093b5014db32fc4fe2c6c7166aa4311296b42e1fa37f52, and its MD5 is b8a767c8fd97ac1bdfdebb2f629e2387. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 18, 2026. Because a file's hash never changes, the identity of TIKTOK 60FPS PATCH.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.