Is 2m.exe safe?
A verified, widely distributed FunPlus executable has minimal antivirus detection, but intrusive runtime indicators and 11 researcher YARA matches warrant caution.
Only 1 of 75 engines flagged the file, and all 17 tier-1 engines were silent; the verified FunPlus signature and broad prevalence also support legitimacy. However, runtime evidence includes process injection, LSASS targeting, and other offensive techniques, while 11 researcher YARA rules matched, so execution should be limited to a verified official release.
9291efc73f2934976c…503f08566fd205Recommended 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.
Only 1 of 75 engines flagged the file, and all 17 tier-1 engines were silent; the verified FunPlus signature and broad prevalence also support legitimacy. However, runtime evidence includes process injection, LSASS targeting, and other offensive techniques, while 11 researcher YARA rules matched, so execution should be limited to a verified official release.
The antivirus result is weak because VBA32 is the sole detector among 75 engines, with no tier-1 detection or family consensus. The file is signed by FunPlus International AG, has been submitted by 2,143 sources, and resembles a previously accepted signer-matched sample. Against that, one completed sandbox run recorded techniques associated with process injection, persistence, privilege elevation, and destructive activity, plus evidence of LSASS targeting. Eleven researcher YARA rules also matched, including rules referencing Sandworm tooling and Cobalt Strike, which is substantial static counter-evidence even though some rules may be broad. No sandbox issued a malicious verdict and no dropped child was identified as malicious, but the child results remain unknown and host-reputation coverage was incomplete. These conflicting signals justify containment and source verification rather than unrestricted execution.
What We Detected
VBA32 was the only engine to flag the sample, reporting Trojan.Win32.ObfBins; the other 74 of 75 engines did not flag it, including all 17 tier-1 engines. The executable carries a verified signature from FunPlus International AG and is widely observed, with 2,143 submitters and 2,423 submissions. One prior signer-matched file also received a safe assessment.
Threat Behavior
A completed sandbox run recorded six offensive techniques, including T1055 process injection, T1547.001 startup persistence, T1548 privilege elevation, and T1485 data destruction. Heuristic evidence additionally reports activity involving lsass.exe, which can indicate credential access. Eleven researcher YARA rules matched, including APT_Sandworm_ArguePatch_Apr_2022_1 and cobalt_strike_tmp01925d3f. No sandbox produced a malicious verdict, and none of 10 inspected children was identified as malicious, although their individual verdicts remain unknown. Only one observed host was reputation-checked despite numerous IP and URL contacts, so no complete host-reputation conclusion is available.
What To Do Now
Use only a copy obtained directly from the official FunPlus release channel and verify that its SHA-256 is 9291efc73f2934976ca8e2dba4f55f64dfd2a4bc0fd4d40e7a503f08566fd205 and its signature remains valid. Keep endpoint protection enabled, and avoid running the file on a production or sensitive system until the unusual runtime activity is explained by the publisher.
Where this verdict could be wrong4 caveats
- VBA32 is the sole detector among 75 engines, and no tier-1 engine identifies ObfBins or another malware family.
- The verified 'FunPlus International AG' signature, widespread prevalence, and one prior signer-matched safe verdict support a legitimate game component.
- behaviour.hasMaliciousSandboxVerdict=false, and no inspected dropped child received a malicious verdict.
- The 11 YARA matches may include broad or collision-prone rules, but their volume and named threat-oriented rules cannot be dismissed.
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/75 engines flagged the sample, and the detector was low-trust
- All 17 tier-1 engines reported clean
- Verified signature from FunPlus International AG
- Common, established sample with 2,143 submitters
- No malicious sandbox verdict or identified malicious child
- 11 researcher YARA rules matched, including Sandworm- and Cobalt Strike-referencing rules
- Runtime evidence maps activity to T1055 process injection
- Heuristic evidence reports access involving lsass.exe
- Six offensive techniques were recorded in one sandbox run
- Observed host-reputation coverage was incomplete
- File reputation is -12
Obtain the executable only from FunPlus's official channel and confirm the signature and hash before use. Keep endpoint protection enabled and quarantine this copy if its origin cannot be verified.
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
Partial1 of 21 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete9 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
- 35MITRE ATT&CK techniques
- 15spawned processes
- 21network contacts
- 34filesystem & 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: Changed an auto-start location that can make code run after sign-in or restart.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
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.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
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.
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.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 9rule hits recorded
- 1 / 75engines flagged
- 2,143sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
6 high-confidence signature or behavior rules matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including VBA32.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has a long, established submission history across 2,143 sources.
ProvenanceDerivedSourceSubmission historyObserved 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
Detection sources at a glance
The available sources did not agree on a named threat category.
One or more independent reference databases matched 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.
- APT_Sandworm_ArguePatch_Apr_2022_1
- cobalt_strike_tmp01925d3f
- DebuggerCheck__API
- DetectEncryptedVariants
- golang_bin_JCorn_CSC846
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
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
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
- Sep 12, 2026, 2:13 PM UTC
9291efc73f2934976ca8e2dba4f55f64dfd2a4bc0fd4d40e7a503f08566fd205Safety & 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 2m.exe safe, or is it malware?
What is 2m.exe?
How many antivirus engines detected 2m.exe?
What should I do if I already ran 2m.exe?
How do I remove 2m.exe?
Is 2m.exe digitally signed?
What is the SHA-256 hash of 2m.exe?
How up to date is this analysis of 2m.exe?
Community
Member reviews and reports for this exact file hash.