File scan report
Verdict Malicious
Is Evergreen Dupe. jar safe? No, we rate this exact file malicious.
Six major antivirus engines identified Java trojan traits, and one sandbox produced a malware verdict with injection and service-related technique mappings.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already opened or ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't opened or run it
Don't open or run this Java file. Delete it, then empty the Recycle Bin or Trash.
If you already opened or ran it
Disconnect the device from the internet, then run a full scan with your security software.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall the operating system.
If you already ran it, do these in order.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
9 of 66 flagged
- Flagged 9
- No detection 57
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 12d ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Nine of the 66 antivirus engines that checked it flagged this JAR, including six major detections that broadly identify a Java Agent trojan. One sandbox also returned a malware verdict, although another returned clean, so the evidence from the test run is supportive rather than unanimous.
The strongest evidence is the combination of nine detections among 75 engines and six major detections. ESET-NOD32 and Fortinet specifically agree on Java/Agent.ADG, while several other engines independently describe a Java Agent or generic Java trojan. The test run adds a malware verdict and maps and T1543.002, but the second sandbox returned clean and no injected target process was recorded. The only observed IP was identified as analysis-environment background traffic, and no complete contacted-host reputation check is available. The lack of external-intelligence corroboration and the ten non-flagging major antivirus engines create uncertainty, but they do not outweigh the converging detections and adverse runtime result.
What We Detected
Nine of the 66 antivirus engines that checked it flagged the JAR, including six major antivirus engines. ESET-NOD32 and Fortinet both identified Java/Agent.ADG, while Avira, F-Secure, Kaspersky, and other engines used Java Agent or generic Java trojan labels. The engines do not establish a strong consensus on one precise family, so Java Agent is the most defensible family description.
Threat Behavior
One of two sandbox runs returned a malware/trojan result, while the other returned clean. Evidence from the test run mapped possible process injection (T1055) and service execution (T1543.002), although no injected target process was identified. The recorded IP contact was analysis-environment background traffic rather than sample activity, and a complete host-reputation check is unavailable. Eight dropped files were observed, but none has a saved verdict, so their status remains unknown.
What To Do Now
Do not run the JAR on a normal system. Quarantine or remove it, keep security software enabled, and obtain a fresh copy only from a verified source if the file was expected.
Where this verdict could be wrong4 caveats
- Ten major antivirus engines did not flag the file, including Microsoft and BitDefender.
- The two sandbox runs disagreed, with one returning clean.
- No malware-specific YARA rules or external-intelligence matches corroborated the detections.
- None of the eight dropped files has a saved malicious verdict; all eight remain unclassified rather than cleared.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Ten major antivirus engines did not flag the file, including Microsoft and BitDefender.
- A second sandbox run returned clean.
- No malware-specific researcher rules or external-intelligence matches were found.
- No dropped file has a saved malicious classification.
- Nine of the 66 antivirus engines that checked it flagged the file, including six major antivirus engines.
- Multiple engines identify a Java Agent trojan, with two agreeing on the Java/Agent.ADG label.
- One sandbox run returned a malware/trojan result.
- The test run mapped possible process injection and service execution techniques.
- The file was first observed only one day before analysis.
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; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 16sandbox rule tags
- 4spawned processes
- 0network contacts
- 18filesystem & 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: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
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 downloading a file, but no download was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service 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.
Threat context
How trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
Evergreen Dupe.jar
fccbe5096eb45bff9ea02e3076323a4b0d65ddda0cb13519c5f81674f4aa01b5
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\sample.jar""
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
6188
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\6188
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 16 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
9 of the 66 antivirus engines that checked it flag it.
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 9
- Avast (major engine)Java:MalwareX-gen [Misc]
- AVG (major engine)Java:MalwareX-gen [Misc]
- Avira (major engine)TR/JAVA.Agent
- ESET-NOD32 (major engine)Java/Agent.ADG trojan
- F-Secure (major engine)Trojan.TR/JAVA.Agent
- Fortinet (major engine)Java/Agent.ADG!tr
- Kaspersky (major engine)HEUR:Trojan.Java.Generic
- CynetMalicious (score: 99)
File fingerprint
- Last analyzed
- Oct 15, 2026, 5:15 AM UTC
- SHA-256
fccbe5096eb45bff9ea02e3076323a4b0d65ddda0cb13519c5f81674f4aa01b5- SHA-1
e386092c4b613aa01c65376829cf9f72fba8bdf2- MD5
3f045abd751148c72588c75308a43dcb
About this file
Evergreen Dupe.jar is a JAR file of 6.2 MB.
- Type and size
- JAR · 6.2 MB
- Signer
- Not applicable
- First seen
- Oct 14, 2026On VirusTotal.
- Submitted by
- 4 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is Evergreen Dupe.jar a virus?
What is Evergreen Dupe.jar?
How many antivirus engines detected Evergreen Dupe.jar?
What should I do if I already opened or ran Evergreen Dupe.jar?
How do I remove Evergreen Dupe.jar?
What kind of malware is Evergreen Dupe.jar?
What is the SHA-256 hash of Evergreen Dupe.jar?
How up to date is this analysis of Evergreen Dupe.jar?
Community
Member reviews and reports for this exact file hash.