Is ManasMinigameMacro.exe safe?
Only two low-trust engines detected this unsigned executable, but its recent appearance, T1486 signal, and unchecked direct-IP traffic warrant caution.
The two detections among 74 engines are generic and come exclusively from low-trust scanners, making a false positive more likely than established malware. However, the unsigned, recently observed executable produced a T1486 signal and contacted two IP addresses whose reputation was not checked, so execution should wait for source verification.
4d1a0f2f0945eee815…57c40371de5ad4Recommended 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 two detections among 74 engines are generic and come exclusively from low-trust scanners, making a false positive more likely than established malware. However, the unsigned, recently observed executable produced a T1486 signal and contacted two IP addresses whose reputation was not checked, so execution should wait for source verification.
APEX and Bkav were the only two of 74 engines to flag the sample, while all 17 tier-1 engines reported no detection. This low-trust-only pattern substantially raises the likelihood of a false positive, and no named malware family has credible consensus. One sandbox run did not issue a malicious verdict, but it recorded T1486 and direct connections to two IP addresses. Because contactedHosts is unavailable, no complete host-reputation conclusion can be drawn from those connections. The file is also unsigned and recently observed, while its single imphash-relative received a prior cautious assessment but lacks signer corroboration. No malicious child, curated intelligence hit, or packing indicator independently confirms malware.
What We Detected
Only 2 of 74 antivirus engines flagged the executable: APEX used a generic malicious label, and Bkav reported W32.Malware.360F8236. Both are low-trust detections, while all 17 tier-1 engines reported no detection and no engine family consensus emerged.
Threat Behavior
One completed sandbox run did not return a malicious sandbox verdict. It nevertheless recorded T1486 and connections to 140.82.114.5 and 140.82.113.5 without an application domain. The direct-IP heuristic is supporting evidence only, and no complete reputation result is available because the contacted-host check was not saved. Ten extracted child files were inspected without a malicious child finding, and no persistence indicators were recorded.
What To Do Now
Verify the exact SHA-256 with the developer or official release source before running it. Keep endpoint protection enabled; if the source cannot establish that hash, avoid execution or test it only in an isolated environment without sensitive accounts or files.
Where this verdict could be wrong3 caveats
- engines.onlyLowTrustFlagging=true and all 17 tier-1 engines reported no detection, which makes the two generic detections likely false positives.
- behaviour.hasMaliciousSandboxVerdict=false and droppedChildren.hasMaliciousChild=false; none of the 10 inspected child files was identified as malicious.
- externalIntel.malwareBazaar.hit=false and externalIntel.yaraify.ruleCount=0 provide no independent malicious-family corroboration, though intelligence coverage can miss new files.
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 2/74 engines detected the sample, both low-trust
- All 17 tier-1 engines reported no detection
- No malicious sandbox verdict was produced
- No malicious child was found among 10 inspected files
- MalwareBazaar, CIRCL, and YARAify supplied no corroborating hit
- Unsigned Win32 executable with no established publisher history
- First observed only one day before analysis
- T1486 appeared among the recorded runtime techniques
- Direct connections to two IP addresses lacked a completed reputation check
- One similar imphash received a prior cautious assessment
Do not run the file until its SHA-256 is confirmed through the developer's official release channel. Keep antivirus and endpoint protection enabled, and isolate any necessary testing from personal data and accounts.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete2 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial2 runtime contacts were observed without a completed reputation cross-check.
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
- 15MITRE ATT&CK techniques
- 4spawned processes
- 2network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Encrypted files or data, behaviour commonly associated with ransomware.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
ManasMinigameMacro.exe
4d1a0f2f0945eee815d5ed127d950611b639cd62df12fff00257c40371de5ad4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
C:\Windows\system32\services.exe
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\ManasMinigameMacro2.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
_avif.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
140.82.114.5
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
140.82.113.5
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.
- 140.82.114.5
- 140.82.113.5
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imagingtk.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\ManasMinigameMacro\config.json.tmp
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
- 6a99bc0128e0c7d6cbbf…cbc6c8Never 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
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
- 2 / 74engines flagged
- 33sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
2 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 41 times from 33 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: ManasMinigameMacro.exe — 4d1a0f2f0945eee815d5ed127d950611b639cd62df12fff00257c40371de5ad4
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — C:\Windows\system32\services.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\ManasMinigameMacro2.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: _avif.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI59202\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 140.82.114.5 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 140.82.113.5 — 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
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The 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.
Evidence140.82.114.5 · 140.82.113.5
2 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- ManasMinigameMacro.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 30.6 MB
- Last analyzed
- Sep 18, 2026, 12:42 PM UTC
4d1a0f2f0945eee815d5ed127d950611b639cd62df12fff00257c40371de5ad4Safety & 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 ManasMinigameMacro.exe safe, or is it malware?
What is ManasMinigameMacro.exe?
How many antivirus engines detected ManasMinigameMacro.exe?
What should I do if I already ran ManasMinigameMacro.exe?
How do I remove ManasMinigameMacro.exe?
What is the SHA-256 hash of ManasMinigameMacro.exe?
How up to date is this analysis of ManasMinigameMacro.exe?
Community
Member reviews and reports for this exact file hash.