File scan report
Verdict Suspicious
Is FNP1119.
This unsigned, Themida-packed 64-bit DLL is flagged by 19 of the 70 antivirus engines that checked it, including five major ones, but no engine names an actual malware family.
Read the whole reasonShow less
Why Suspicious? 19 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Avoid loading this DLL unless it comes from a vendor you trust and you can verify its source. If its origin is unclear, delete it and scan your system.
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 use 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 used 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
19 of 70 flagged
- Flagged 19
- No detection 51
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
5 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
19 of the 70 antivirus engines that checked it flagged this DLL, including ESET, Symantec, Sophos, Fortinet and Trellix. Their labels are generic, packer-based or describe it as unwanted, rather than naming a specific malware family. The file is unsigned and heavily packed with anti-analysis features, and only three sources have submitted it, so it should not be trusted without a known origin.
Five major antivirus engines and fourteen others flagged this file, which is too much agreement to dismiss. However, the major labels describe a Themida-protected suspicious application, a reputation-based unwanted program, riskware, or a generic trojan, and they do not agree on any family. The DLL carries no signature and is wrapped in Themida, with very high entropy and tags for debugger detection and long sleeps that are typical of evasive code. The sandbox run recorded no process injection and no network contacts, and returned no malicious verdict, so evidence from the test run does not confirm harmful behaviour. Together with its rare distribution since it was first seen on Jul 23, 2026, this leaves a risky but unconfirmed picture.
What We Detected
19 of the 70 antivirus engines that checked it flagged this 64-bit DLL. They include ESET-NOD32 (Themida-packed suspicious application), Symantec (generic trojan), Sophos (reputation-based unwanted program), Fortinet (riskware) and Trellix (generic reputation). No consistent malware family emerges from these labels. The file is unsigned and protected with Themida, and its code sections have very high entropy.
Threat Behavior
The sandbox runs show the DLL being launched through rundll32 with several exported functions. No injection into other processes and no network connections were recorded, and no malicious sandbox verdict was returned. Its tags indicate debugger detection and long sleeps, which can let malware evade analysis but are also features of commercial protectors. No complete reputation check of contacted hosts is available.
What To Do Now
Do not load or run this DLL unless you know exactly which trusted application it belongs to and where it came from. If it appeared unexpectedly, remove it and run a full scan with your security software kept enabled.
Where this verdict could be wrong2 caveats
- Many detections name only a packer, a reputation bucket or a potentially unwanted program, which suggests that a legitimately protected but obscure DLL is drawing rule-based hits.
- 12 major antivirus engines, including BitDefender, Avira and DrWeb, did not flag the file.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No process injection or network connections were recorded in the sandbox runs
- No detection names a specific malware family
- 19 of the 70 antivirus engines that checked it flagged it, including five major antivirus engines
- The DLL is unsigned, so no publisher identity backs it
- It is heavily packed with Themida, which hides its code
- Its tags indicate debugger detection and long delays that can evade analysis
- Only three sources have submitted it
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 20sandbox rule tags
- 9spawned processes
- 0network contacts
- 24filesystem & 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: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Checked which security software was installed 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.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
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 weakening security settings; no setting change 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 5: FileSeen in the test run
FNP1119.dll
29d0c97e172b85781a415dc7ff316ca8ed1426d79a5295a93b13e156356f9b01
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
rundll32.exe
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\FNP1119.dll",#1
Test run - Evidence 3 of 5: ProcessSeen in the test run
loaddll64.exe
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\FNP1119.dll"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
mntemp
C:\ProgramData\mntemp
Test run - Evidence 5 of 5: Written fileSeen in the test run
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 20 mapped techniques, every process, file, registry and network entry and 1 dropped file.
Show the technical evidenceChapter 04
Technical details
19 of the 70 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 19
- ESET-NOD32 (major engine)Win64/Packed.Themida.L suspicious application
- Fortinet (major engine)Riskware/Application
- Sophos (major engine)Generic Reputation PUA (PUA)
- Symantec (major engine)Trojan.Gen.MBT
- TrellixENS (major engine)Artemis!7BD5420E68E4
- alibabacloudVirTool:Win/Wacapew.A9nj
- Antiy-AVLGrayWare/Win32.Wacapew
- BkavW32.Malware.7AAB534D
File fingerprint
- Last analyzed
- Sep 7, 2026, 11:52 AM UTC
- SHA-256
29d0c97e172b85781a415dc7ff316ca8ed1426d79a5295a93b13e156356f9b01- SHA-1
7f1db7998485eb37b21d98a1e8111fd834b8b179- MD5
7bd5420e68e400b7e842a79d0c612793
About this file
FNP1119.dll is a Win32 DLL file of 5.6 MB.
- Type and size
- Win32 DLL · 5.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 23, 2026On VirusTotal.
- Submitted by
- 3 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- Themida (VirusTotal tag)Packing hides code; legitimate installers use it too.
- Entropy
- 7.61 of 8A code section is highly compressed or encrypted.
First scanned Updated
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 FNP1119.dll safe, or is it malware?
What is FNP1119.dll?
How many antivirus engines detected FNP1119.dll?
I already downloaded and used FNP1119.dll — what should I do?
What is the SHA-256 hash of FNP1119.dll?
How up to date is this analysis of FNP1119.dll?
Community
Member reviews and reports for this exact file hash.