File scan report
Verdict Suspicious
Is MA2 Dual NSP Emulator v1.
This Python-packaged emulator tool draws 4 of 74 engine detections, including a keylogger label and one major generic trojan hit, and its signature fails verification.
Read the whole reasonShow less
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Only run this tool if it came directly from a source you trust, ideally inside a virtual machine, and keep your antivirus enabled throughout.
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
4 of 69 flagged
- Flagged 4
- No detection 65
- No result 5
- Code signing Signer not verified
- Test run Completed
- First seen 2y ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Four of the 69 antivirus engines that checked it flag this program. They include TrendMicro's generic trojan label and Zillya's keylogger label, while most major engines stay silent. The file carries a signature that fails verification and is a packaged Python application. It has circulated since January 2024 among many submitters, so a false positive is plausible, but the evidence is not clean enough to clear it.
Four of the 69 antivirus engines that checked it flagged the file. One is a major antivirus engine with a generic trojan label, and Zillya calls it a keylogger script, but no family consensus exists. The embedded signature names the product itself and chains to an untrusted root, so it proves nothing about the author. The sandbox summary showed a Python application unpacking its modules, with no high-risk techniques, no injection target and no network contact of its own. The file was first seen on Jan 25, 2024 and has 129 distinct submitters, which supports a niche-tool explanation. One related file built with the same import table was previously judged malicious. With detections and benign context pointing both ways, caution is warranted.
What We Detected
4 of the 69 antivirus engines that checked it flagged this executable. They are TrendMicro-HouseCall with a generic Win64 trojan label, Zillya with a keylogger script label, CrowdStrike with a 70% machine-learning confidence score, and one less reliable engine. Sixteen major antivirus engines reported nothing. The file carries a code signature naming the product, but it fails verification because the certificate chains to an untrusted root.
Threat Behavior
The sandbox runs show a Python-packaged program that unpacks imaging and Windows support modules into a temporary folder. No high-risk techniques, process injection targets, persistence or contacts of the sample's own were recorded. No completed reputation check of contacted hosts is available. The file was first seen on Jan 25, 2024 and has been submitted by 129 sources.
What To Do Now
Run it only if you obtained it from the tool's original author and trust that source. Prefer running it in a virtual machine, and keep your antivirus enabled. If you are unsure of where it came from, delete it.
Where this verdict could be wrong2 caveats
- 129 distinct submitters over more than two years and silence from 16 major antivirus engines are consistent with a niche hobbyist tool that is falsely flagged.
- The only major detection is a generic label, and no sandbox run returned a malicious verdict.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Submitted by 129 sources since January 2024
- No high-risk techniques, injection targets or persistence recorded in the sandbox runs
- 16 major antivirus engines did not flag it
- A major antivirus engine flags it with a generic trojan label
- One engine labels it a keylogger
- The signature fails verification and chains to an untrusted root
- A file with the same import table was previously judged malicious
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 18sandbox rule tags
- 4spawned processes
- 4network contacts
- 30filesystem & 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).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Unpacked hidden content while it ran.
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Contacted a server on an unusual network port.
Note: Listed the programs running on the test computer.
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.
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 7: FileSeen in the test run
MA2 Dual NSP Emulator v1.2.exe
06523ef39767e6dfd4ccb07d43c0f94e3db4282d4f78dfd4accb97480a04e08b
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
MA2 Dual NSP Emulator v1.2.exe
Test run - Evidence 3 of 7: ProcessSeen in the test run
06523ef39767e6dfd4ccb07d43c0f94e3db4282d4f78dfd4accb97480a04e08b.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
_imaging.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI3362\PIL\_imaging.cp312-win_amd64.pyd
Test run - Evidence 5 of 7: Written fileSeen in the test run
_imagingcms.cp312-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI3362\PIL\_imagingcms.cp312-win_amd64.pyd
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
23.49.140.110
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
104.98.118.146
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 18 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
4 of the 69 antivirus engines that checked it flag it; a signature that did not verify.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 4
- TrendMicro-HouseCall (major engine)Trojan.Win64.Gen.TL0101DO26ZB
- APEXMalicious
- CrowdStrikewin/malicious_confidence_70% (W)
- ZillyaTrojan.Keylogger.Script.265
File fingerprint
- Last analyzed
- Sep 3, 2026, 5:41 PM UTC
- SHA-256
06523ef39767e6dfd4ccb07d43c0f94e3db4282d4f78dfd4accb97480a04e08b- SHA-1
4df6ab268dab00c3fe814ece417d09faa45ae7a6- MD5
6430f26e152f412882337a603d6c9920
About this file
MA2 Dual NSP Emulator v1.2.exe is a Win32 EXE file of 18.6 MB.
- Type and size
- Win32 EXE · 18.6 MB
- Signer
- MA2 Dual NSP Emulator (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
- First seen
- Jan 25, 2024On VirusTotal.
- Submitted by
- 129 distinct sources
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned Updated
Includes every engine result (74), 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 7 questions people ask most about this file.
Is MA2 Dual NSP Emulator v1.2.exe safe, or is it malware?
What is MA2 Dual NSP Emulator v1.2.exe?
How many antivirus engines detected MA2 Dual NSP Emulator v1.2.exe?
What should I do if I already ran MA2 Dual NSP Emulator v1.2.exe?
Is MA2 Dual NSP Emulator v1.2.exe digitally signed?
What is the SHA-256 hash of MA2 Dual NSP Emulator v1.2.exe?
How up to date is this analysis of MA2 Dual NSP Emulator v1.2.exe?
Community
Member reviews and reports for this exact file hash.