File scan report
Verdict Suspicious
Is Anime Adventures Macro. exe safe? Treat it as suspicious.
Three generic detections and an unsigned, short history warrant caution, although sandbox evidence and major antivirus engines provide no corroborated malware behavior.
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it, but no major engine agrees; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Verify the download against an official publisher-provided hash or release before use. Keep security protection enabled and avoid running it on a system containing valuable accounts or data until its provenance is established.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 71 flagged
- Flagged 3
- No detection 68
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 10d ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Three of the 71 antivirus engines that checked it flagged this unsigned executable, but all labels are generic and none came from a major antivirus engine. The sandbox runs recorded no malicious verdict, named injection target, persistence, or sample-generated network contact, so the evidence suggests caution rather than a confirmed malware family.
Three of the 71 antivirus engines that checked it flagged the executable, including one mid-tier detector and two less reliable detectors. Their labels are generic, and no major antivirus engines identified malware or agreed on a family. The sandbox runs did not produce a malicious verdict or record a named injection target; the mapping therefore does not establish process injection. The only recorded contacts were analysis-machine background traffic, while the host-reputation check found no known harmful entry among the observed hosts. However, the executable is unsigned and was first seen on Oct 28, 2026, so there is no verified publisher or long distribution history to outweigh the detections conclusively.
What We Detected
Three of the 71 antivirus engines that checked it flagged the executable. Gridinsoft used a generic rule-based trojan label, while APEX and Bkav supplied generic malicious labels; no major antivirus engines flagged it and no real malware family was identified.
Threat Behavior
A T1055 mapping appeared without the artifact needed to show actual injection. The recorded contacts were background traffic from the analysis environment rather than activity attributable to the sample, and the available host-reputation check found no known harmful host.
What To Do Now
Do not run the executable on an important system until its origin and publisher can be verified. Keep security software enabled and, if testing is necessary, use an isolated environment without personal accounts or sensitive files.
Where this verdict could be wrong2 caveats
- Three independent engines flagged the executable, including Gridinsoft, so the detections cannot be dismissed as purely less-reliable-engine noise.
- The file is unsigned and was first seen on Oct 28, 2026, leaving little publisher or age-based evidence to establish provenance.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the major antivirus engines flagged the executable.
- The sandbox runs recorded no malicious verdict, named injection target, or persistence indicator.
- No malware-specific community rules or public sample-database entry matched the hash.
- The antivirus analysis found no evidence that the executable's code was packed.
- Three independent antivirus engines flagged the executable with generic malicious or trojan labels.
- The executable has no verified digital signature identifying its publisher.
- It was first seen on Oct 28, 2026 and has only 27 distinct submitters, providing limited distribution history.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 2 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 2isolated sandbox runs
- 11sandbox rule tags
- 2spawned processes
- 0network contacts
- 23filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
AnimeAdventuresMacro.exe
663d4a0558da48e119f62648e1e54c674dd00ead2b1e1975417c4072826209ad
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
AnimeAdventuresMacro.exe
"C:\Users\<USER>\Desktop\AnimeAdventuresMacro.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
AnimeAdventuresMacro.exe
"C:\Users\user\Desktop\AnimeAdventuresMacro.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
SpiritTown.png
C:\Users\<USER>\Desktop\Images\Defaults\SpiritTown.png
Test run - Evidence 5 of 5: Written fileSeen in the test run
HauntedMansion.png
C:\Users\<USER>\Desktop\Images\Defaults\HauntedMansion.png
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 11 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
3 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- APEXMalicious
- BkavW32.Malware.FC49A561
- GridinsoftTrojan.Heur!.02016023
File fingerprint
- Last analyzed
- Oct 28, 2026, 9:40 PM UTC
- SHA-256
663d4a0558da48e119f62648e1e54c674dd00ead2b1e1975417c4072826209ad- SHA-1
5a2967feda670dfa5905abfb51340d9261998dc9- MD5
c2660329692eabd65aa5ba91d29f66ff
About this file
AnimeAdventuresMacro.exe is a Win32 EXE file of 39.0 MB.
- Type and size
- Win32 EXE · 39.0 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 28, 2026On VirusTotal.
- Submitted by
- 27 distinct sources
- Packer
- None detected
- Entropy
- 7.75 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is AnimeAdventuresMacro.exe safe, or is it malware?
What is AnimeAdventuresMacro.exe?
How many antivirus engines detected AnimeAdventuresMacro.exe?
I already downloaded and ran AnimeAdventuresMacro.exe — what should I do?
What is the SHA-256 hash of AnimeAdventuresMacro.exe?
How up to date is this analysis of AnimeAdventuresMacro.exe?
Community
Member reviews and reports for this exact file hash.