Is ManasMinigameMacro.exe safe?
Only two low-trust engines detected this unsigned executable, but process-injection, LSASS-related, and direct-IP activity warrant caution until independently explained.
The antivirus pattern strongly suggests false positives: only 2 of 74 engines flagged the file, neither from the high-trust group. However, one sandbox recorded process-injection and LSASS-related indicators plus direct-IP traffic, and the executable lacks a verified signature, so it should not be run on a primary system without further validation.
dd706f048df4033686…8fcf9a904afb40Recommended 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 suggests false positives: only 2 of 74 engines flagged the file, neither from the high-trust group. However, one sandbox recorded process-injection and LSASS-related indicators plus direct-IP traffic, and the executable lacks a verified signature, so it should not be run on a primary system without further validation.
Only APEX and Bkav flagged the sample among 74 engines, while all 17 high-trust engines that reported results found no detection. That pattern ordinarily points toward false positives, and no named malware family reached consensus. However, the completed sandbox run mapped activity to T1055 and T1486 and produced an LSASS-related credential-dumping heuristic. Three direct IP contacts were also recorded, but no complete host-reputation result is available because the contacted-host cross-check was not saved. The executable is unsigned and newly observed, which limits publisher-based assurance. With no malicious child, sandbox verdict, or external-intelligence match, the evidence supports caution rather than a definitive malware attribution.
What We Detected
APEX and Bkav flagged the file, giving a total of 2 detections across 74 engines. Neither is a high-trust detection, all 17 reporting high-trust engines were silent, and no malware family consensus emerged. The executable is unsigned and has no established publisher history.
Threat Behavior
One completed sandbox run mapped activity to process injection (T1055) and T1486 and raised an LSASS-related credential-dumping heuristic. It also recorded direct connections to three IP addresses. These are meaningful risk indicators, but there was no malicious sandbox verdict, none of the 10 inspected child files was confirmed malicious, and no complete host-reputation cross-check is available for the observed IP addresses.
What To Do Now
Do not run the file on a primary or sensitive computer until its origin and behavior are verified. Keep endpoint protection enabled, obtain the executable from the developer's documented release channel, compare its SHA-256 hash with a publisher-provided value, and test it only in an isolated environment if further analysis is necessary.
Where this verdict could be wrong3 caveats
- engines.onlyLowTrustFlagging=true with 17 tier-1 engines reporting no detection makes the two generic detections likely false positives.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after 10 children were inspected.
- externalIntel reports no CIRCL, MalwareBazaar, or YARAify hit, although absence of such hits does not establish benignity.
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 of 74 engines detected the file, both low-trust
- engines.tier1Malicious=0, with 17 high-trust engines reporting no detection
- No malicious sandbox verdict was recorded
- No malicious child was found among 10 inspected dropped files
- No CIRCL, MalwareBazaar, or YARAify corroboration was found
- Unsigned Win32 executable with no verified publisher history
- Sandbox mapping to process injection technique T1055
- LSASS-related activity raised a credential-dumping heuristic
- Direct connections to three IP addresses without a completed reputation cross-check
- File was first observed very recently
- Two prior imphash-related samples also received cautious assessments
Keep endpoint protection enabled and avoid running this file on a primary system. Verify the hash and source with the developer, or analyze it in an isolated sandbox before use.
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
Partial3 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
- 17MITRE ATT&CK techniques
- 11spawned processes
- 3network 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: 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.
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
dd706f048df403368629592edc28768b0dd7afdcdc90172d0d8fcf9a904afb40
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\_MEI54122\PIL\_avif.cp312-win_amd64.pyd
04Isolated runtime analysis - Written fileObserved
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_imaging.cp312-win_amd64.pyd
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
140.82.112.5
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
140.82.114.6
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.5
- 140.82.114.6
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_avif.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_imaging.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_imagingcms.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_imagingmath.cp312-win_amd64.pyd
- C:\Users\<USER>\AppData\Local\Temp\_MEI54122\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
- 12sources 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 12 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: ManasMinigameMacro.exe — dd706f048df403368629592edc28768b0dd7afdcdc90172d0d8fcf9a904afb40
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\_MEI54122\PIL\_avif.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _imaging.cp312-win_amd64.pyd — C:\Users\<USER>\AppData\Local\Temp\_MEI54122\PIL\_imaging.cp312-win_amd64.pyd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 140.82.112.5 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 140.82.114.6 — 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.5 · 140.82.114.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.6 MB
- Last analyzed
- Sep 19, 2026, 2:36 AM UTC
dd706f048df403368629592edc28768b0dd7afdcdc90172d0d8fcf9a904afb40Safety & 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.