File scan report
Verdict Suspicious
Is Koaloader. dll safe? Treat it as suspicious.
An unsigned DLL-proxy loader linked to game DLC unlocking, flagged by 48 of the 71 antivirus engines that checked it with mostly generic trojan labels and no malicious sandbox…
Read the whole reasonShow less
Why Suspicious? 48 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Avoid this file unless you knowingly use this game-unlocking loader from its original source, and keep your antivirus enabled rather than creating exclusions for it.
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
48 of 71 flagged
- Flagged 48
- No detection 23
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This DLL matches a known loader used to unlock paid game content by hijacking DLL loading. Engines including BitDefender, Microsoft and Fortinet flag it, mostly with generic labels, while Ikarus calls it a potentially unwanted loader. The sandbox runs recorded no malicious activity, but the file is unsigned and tied to piracy tooling.
48 of the 71 antivirus engines that checked it flag this file, including nine major antivirus engines, but the labels are mostly generic buckets rather than a named malware family. Ikarus identifies it as a potentially unwanted Koala loader. Across four sandbox runs, no malicious verdict, injection target or sample-owned network contact was recorded; the observed traffic was the analysis machine's own background activity. The file is unsigned and associated with piracy tooling, which carries real risk, but the evidence does not show clear malicious payload behaviour.
What We Detected
48 of the 71 antivirus engines that checked it flag this unsigned 32-bit DLL. Major detections include BitDefender (Generic.Trojan.Koder.Marte), Microsoft (Trojan:Win32/Tnega!MSR), Fortinet and Sophos, mostly with generic labels. Ikarus labels it PUA.KoalaLoader, and McAfee labels it a DLL-hijacking trojan.
Threat Behavior
The file behaves like a DLL-proxy loader of the kind used to unlock game DLC. Four sandbox runs recorded no malicious verdict, no named injection target and no network activity of the sample's own. The contacted addresses belong to the analysis machine's background traffic. The file has been widely seen since early 2023 and has no public malware-database listing.
What To Do Now
Only keep this file if you deliberately installed this game-unlocking tool and understand the risk. Copies from piracy sources can be tampered with. If you did not intend to install it, delete it and run a full scan, keeping your security software enabled.
Where this verdict could be wrong2 caveats
- Most detections are generic labels, and no sandbox run recorded malicious activity, so the file may be only the intended game-unlocking loader.
- Some 'Koder' labels may reflect real trojanised copies circulating under this name, so the detections cannot be dismissed entirely.
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 malicious verdict in four sandbox runs
- Widely seen by over 1,200 submitters since 2023
- No public malware-database or malware-specific rule matches
- Flagged by 48 of the 71 antivirus engines that checked it, including nine major antivirus engines
- Unsigned DLL designed to hijack how games load libraries
- Associated with game piracy and DLC-unlocking tools, which are often redistributed in tampered form
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 4 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 4isolated sandbox runs
- 21sandbox rule tags
- 15spawned processes
- 2network contacts
- 40filesystem & 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 network settings of the test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
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 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 7: FileSeen in the test run
Koaloader.dll
2665a951793eac577c89d9115aff15b3c69f87af4da15a93a81200c890a4cd00
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1
Test run - Evidence 3 of 7: ProcessSeen in the test run
loaddll32.exe
C:\Windows\System32\loaddll32.exe loaddll32.exe "C:\Users\user\Desktop\readme.dll"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
Temp
C:\ProgramData\Microsoft\Windows\WER\Temp
Test run - Evidence 5 of 7: Written fileSeen in the test run
ef396630-f986-4029-bdee-e49fe8f0dc98
C:\ProgramData\Microsoft\Windows\WER\Temp\ef396630-f986-4029-bdee-e49fe8f0dc98
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
20.189.173.20
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
20.189.173.21
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 21 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
48 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 48
- Avast (major engine)Win32:MalwareX-gen [Bd]
- AVG (major engine)Win32:MalwareX-gen [Bd]
- BitDefender (major engine)Generic.Trojan.Koder.Marte.A.16B3CFD5
- Emsisoft (major engine)Generic.Trojan.Koder.Marte.A.16B3CFD5 (B)
- Fortinet (major engine)W32/Agent.AAWO!tr
- GData (major engine)Generic.Trojan.Koder.Marte.A.16B3CFD5
- Ikarus (major engine)PUA.KoalaLoader
- Microsoft (major engine)Trojan:Win32/Tnega!MSR
File fingerprint
- Last analyzed
- Oct 18, 2026, 5:08 PM UTC
- SHA-256
2665a951793eac577c89d9115aff15b3c69f87af4da15a93a81200c890a4cd00- SHA-1
638669c749cd493c4407e8c674ecff60a317da80- MD5
7e92b09ee4fe34c50415140a0c1130ab
About this file
Koaloader.dll says it is https://github.com/acidicoala/Koaloader (Koaloader), 2.2 MB.
- Claims to be
- https://github.com/acidicoala/Koaloader (Koaloader)From the file's own version information, written by whoever built it.
- Original name
- Koaloader.dllMatches the shared file name.
- Type and size
- Win32 DLL · 2.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jan 15, 2023On VirusTotal.
- Submitted by
- 1,224 distinct sources
- Packer
- None detected
- Entropy
- 6.20 of 8
First scanned Updated
Verdict history
- Not fully confirmed
- Suspiciousafter 2 more engines flagged it
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
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 Koaloader.dll safe, or is it malware?
What is Koaloader.dll?
How many antivirus engines detected Koaloader.dll?
What should I do if I already used Koaloader.dll?
What is the SHA-256 hash of Koaloader.dll?
How up to date is this analysis of Koaloader.dll?
Community
Member reviews and reports for this exact file hash.