Our call: Is 2m.exe safe?Safe
Signed by FunPlus International AG with zero engine detections and a prior clean verdict for the same signer.
- 0 of 74 antivirus engines flagged the file.Observed · Antivirus analysis
- The hash has a long, established submission history across 1,645 sources.Derived · Submission history
- One or more independent reference checks were incomplete or unavailable.Derived · External-intelligence coverage
9291efc73f2934976c…08566fd205Recommended 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.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete4 signature or behavior rules matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
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
2m.exe
9291efc73f2934976ca8e2dba4f55f64dfd2a4bc0fd4d40e7a503f08566fd205
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\executable.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Users\<USER>\AppData\Local\Temp\ts.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
fnd_tmp.dl
C:\Users\<USER>\AppData\Local\Temp\fnd_tmp.dl
04Isolated runtime analysis - Written fileObserved
ts.exe
C:\Users\<USER>\AppData\Local\Temp\ts.exe
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
52.42.146.143
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
23.38.194.45
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.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 1,645 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: 2m.exe — 9291efc73f2934976ca8e2dba4f55f64dfd2a4bc0fd4d40e7a503f08566fd205
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\executable.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Users\<USER>\AppData\Local\Temp\ts.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: fnd_tmp.dl — C:\Users\<USER>\AppData\Local\Temp\fnd_tmp.dl
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: ts.exe — C:\Users\<USER>\AppData\Local\Temp\ts.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 52.42.146.143 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 23.38.194.45 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
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.
Zero of 74 engines flagged the file. The executable is signed by FunPlus International AG, which has a clean historical sample, and sandbox plus network checks returned no malicious indicators.
The complete absence of malicious detections across 74 engines, including 17 tier-1 engines, combined with a verified certificate from FunPlus International AG, strongly supports a benign classification. A prior identical-signer sample received a safe verdict under the same reason code. Although sandbox artefacts triggered heuristics for process injection and LSASS access, these remain unconfirmed by any engine or external intelligence. Contacted hosts and dropped children also show no malicious reputation.
What We Detected
74 engines scanned the 1 MB Win32 executable; none returned a malicious or suspicious result. The file carries a valid code-signing certificate issued to FunPlus International AG. Sandbox execution wrote ten dropped files and contacted 19 IP addresses, yet none of those hosts or children carry known-malicious verdicts in our cache.
Threat Behavior
Observed MITRE techniques include T1055 (process injection), T1485 (data destruction) and LSASS access, but these remain heuristic mappings without corroborating engine labels or external-intel hits. No persistence registry keys or malicious mutexes were recorded.
What To Do Now
The file can be executed under standard security policies. Keep endpoint protection enabled; no additional action is required based on current evidence.
Where this verdict could be wrong2 caveats
- Community comments contain conflicting researcher tags (suspicious, bootkit, cobalt-strike) but these are unverified annotations without engine corroboration.
- Sandbox observed T1055 process injection and LSASS access, which could indicate malicious behaviour if the heuristics were confirmed by tier-1 detections.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero engine detections across 74 scanners
- Verified signer with clean historical sample
- No malicious children or contacted hosts
The sample shows no malicious indicators; it can be considered safe to use while maintaining normal endpoint protection.
Behavior
Plain-English impact first, then the observed runtime evidence.
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.
- 52.42.146.143
- 23.38.194.45
- 43.163.62.120
- 23.38.194.75
- 23.38.194.74
- 49.51.67.112
- 47.252.117.159
- 127.0.0.1
- 184.51.252.167
- 44.242.31.69
- http://store-account.funplus.com/api/account/uid_list
- C:\Users\<USER>\AppData\Local\Temp\fnd_tmp.dl
- C:\Users\<USER>\AppData\Local\Temp\ts.exe
- C:\Users\<USER>\AppData\Local\Temp\fpx_for_ss.dll
- C:\Program Files (x86)\FunPlus\Tiles Survive\Font\FZYaSong-B-GBK.ttf
- C:\Program Files (x86)\FunPlus\Tiles Survive\Font\Source Han Sans SC.ttf
- C:\Users\<USER>\AppData\Local\Temp\fnd_tmp.dl
- C:\Program Files (x86)\FunPlus\Tiles Survive\1.0.0.871\libs\wesight\crashsight_data\crashsight_data_db-journal
- C:\Users\<USER>\AppData\LocalLow\Kingsgroup\test.exe
- C:\Program Files (x86)\FunPlus\Tiles Survive\download\5c1a1e42dce21ae6359078200c035c4e.7z.FPXDownloader
- C:\Program Files (x86)\FunPlus\Tiles Survive\download\5c1a1e42dce21ae6359078200c035c4e.7z.efdindex
- dc_launcher
- Global\{D90D5747-26D3-417C-AC5E-01EA742C5633}Tiles Survive!
- cversions.3.m
- FPX_CLIENT_ts_pc_global_prod.win.mutex
- \Sessions\1\BaseNamedObjects\dc_launcher
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- ac3706ebbb78cfba74e5…0aba8fNever scannednever seen before
- 96ad1146eb96877eab59…87dcf7Never scannednever seen before
- 1ebdce1ec3a1f3ac003b…9dcd68Never scannednever seen before
- a3b5b0a62acc5a4bd272…9c1596Never scannednever seen before
- 2c2d8bb0b3769e61be19…3dec38Never scannednever seen before
- ae4e0a9c02913281c0ed…1041faNever scannednever seen before
- 5539033651257e42457e…0c6d96Never scannednever seen before
- 8735334017b138f7077e…049408Never scannednever seen before
- 2f9d51c36a519cfc2a03…c6da75Never scannednever seen before
- 4cdfc3f9e35c1c4caad3…648e54Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
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.
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.
Sample spawned wmic with Process.Create / XSL — WMI is a common execution proxy for malware trying to evade process-tree monitoring.
Evidencewmic OS get Version /VALUEThe 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.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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.
Evidence52.42.146.143 · 23.38.194.45 · 43.163.62.120
0 of 74 engines flagged this file
View all 74 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
- 2m.exe
- Format
- Win32 EXE
- Code signing
- Signature valid: FunPlus International AG
- Size
- 994.4 KB
- Last analyzed
- Aug 1, 2026, 4:48 AM UTC
9291efc73f2934976ca8e2dba4f55f64dfd2a4bc0fd4d40e7a503f08566fd205Safety & 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.
Run it only when it came from the developer's official site or another source you independently trust.
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
Keep your antivirus and Windows updates switched on so you stay protected.