Is ManasMinigameMacro.exe safe?
Only 2 of 74 engines flagged this unsigned executable, but possible process injection, LSASS-related activity, and unchecked direct-IP contacts warrant caution.
The antivirus pattern strongly resembles a false positive: only APEX and Bkav detected it, while all 17 tier-1 engines remained silent. However, one runtime analysis mapped possible process injection and LSASS-related activity, and the two contacted IP addresses were not reputation-checked, so execution should be deferred pending further verification.
5c1e41d6f9718c6dd7…61a339bf05be18Recommended 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 antivirus pattern strongly resembles a false positive: only APEX and Bkav detected it, while all 17 tier-1 engines remained silent. However, one runtime analysis mapped possible process injection and LSASS-related activity, and the two contacted IP addresses were not reputation-checked, so execution should be deferred pending further verification.
Only 2 of 74 engines raised generic detections, both from low-trust engines, while no tier-1 engine identified malware or a family. That pattern ordinarily supports a false-positive explanation. Counterbalancing it, the completed runtime observation mapped activity to T1055 and surfaced LSASS-related process activity, although it produced no malicious sandbox verdict and did not prove credential access. The executable is unsigned and newly observed, so there is no publisher identity or historical signer record to reduce uncertainty. It also contacted two IP addresses, but no complete host-reputation result is available. With no malicious child, curated intelligence hit, or family consensus, the evidence warrants caution rather than a definitive malware attribution.
What We Detected
APEX and Bkav flagged the file, producing 2 detections across 74 engines. Both are low-trust detections with generic labels; all 17 tier-1 engines reported no detection, and no malware family consensus emerged. The executable is unsigned and has no established signer history.
Threat Behavior
One completed runtime observation mapped possible process injection to MITRE T1055 and surfaced LSASS-related process activity. These are meaningful risk indicators, but the saved evidence does not prove memory theft or a specific injection method, and the sandbox issued no malicious verdict. The sample contacted 140.82.112.6 and 162.159.36.2 directly; because the host-reputation cross-check was not completed or saved, those contacts cannot be characterized as benign or malicious. Ten extracted children were inspected without a malicious child being identified, although their individual verdicts remained unknown.
What To Do Now
Do not run the executable on a production or personal system until its source and intended publisher are independently verified. Keep endpoint protection enabled, obtain the file from an official release channel if one exists, and use an isolated analysis environment for any necessary testing.
Where this verdict could be wrong4 caveats
- The 2/74 detections come exclusively from APEX and Bkav, with all 17 tier-1 engines reporting no detection.
- behaviour.hasMaliciousSandboxVerdict=false, so the single runtime analysis did not produce an explicit malicious conclusion.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false provide no researcher-curated corroboration.
- The lsass.exe and svchost.exe entries may reflect process observation rather than proven memory access or injection; the saved T1055 mapping does not establish the exact method.
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 file, both low-trust.
- engines.tier1Malicious=0 across 17 tier-1 engines.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false after 10 children were inspected.
- YARAify, CIRCL, and MalwareBazaar returned no corroborating hit.
- Runtime evidence mapped possible process injection to T1055.
- A credential-dumper heuristic associated activity with lsass.exe.
- Two direct IP contacts lack a completed reputation cross-check.
- The Win32 executable is unsigned and has no signer history.
- The file was first observed very recently.
Avoid running this file until its origin and publisher can be verified or additional analysis resolves the T1055 and LSASS-related signals. Keep endpoint protection enabled and test only in an isolated environment.
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
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
- 16MITRE ATT&CK techniques
- 11spawned processes
- 2network contacts
- 17filesystem & 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: 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
5c1e41d6f9718c6dd7e34a468f599fd94a529c16dcd63ea35a61a339bf05be18
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\ManasMinigameMacro.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /c "ver"
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\_MEI42282\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
140.82.112.6
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
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.112.6
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imagingtk.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\ManasMinigameMacro\config.json.tmp
- Global\OneSettingQueryMutex+compat+encapsulation
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.
- 3rule hits recorded
- 2 / 74engines flagged
- 13sources 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
2 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 14 times from 13 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: ManasMinigameMacro.exe — 5c1e41d6f9718c6dd7e34a468f599fd94a529c16dcd63ea35a61a339bf05be18
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\ManasMinigameMacro.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\cmd.exe /c "ver"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: _avif.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI42282\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 140.82.112.6 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — 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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The 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\System32\svchost.exe -k NetworkService -pSandbox 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.
Evidence140.82.112.6 · 162.159.36.2
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.5 MB
- Last analyzed
- Sep 15, 2026, 10:20 PM UTC
5c1e41d6f9718c6dd7e34a468f599fd94a529c16dcd63ea35a61a339bf05be18Safety & 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?
I already downloaded and ran ManasMinigameMacro.exe — what should I do?
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.