Is DupeMod.jar safe?
No antivirus engine detected this recent JAR, but one sandbox mapped three offensive techniques, including possible process injection and defense impairment.
None of 75 antivirus engines flagged the JAR, and its single sandbox run produced no malicious sandbox verdict or confirmed harmful child. However, runtime mappings to T1055, T1543.002, and T1562.001 warrant caution because the file is only one day old and lacks supporting history.
5a052f7071b9e66a6f…364731ddecc306Recommended next actions
Before opening or running
Do not open or run it until the source and publisher can be verified independently.
If you already opened or ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
None of 75 antivirus engines flagged the JAR, and its single sandbox run produced no malicious sandbox verdict or confirmed harmful child. However, runtime mappings to T1055, T1543.002, and T1562.001 warrant caution because the file is only one day old and lacks supporting history.
The strongest reassuring evidence is that 0 of 75 engines detected the sample, including no detections from 17 tier-1 engines. One completed sandbox run did not issue a malicious verdict, and the fully covered contacted host was not present in the malicious or suspicious URL cache. Against that, the runtime report mapped activity to T1055, T1543.002, and T1562.001, which are meaningful offensive-technique signals even though the process-injection mapping is not definitive. None of nine inspected children was confirmed harmful, but all nine retain unknown individual verdicts. Because this JAR is only one day old and has no similar-file history, the clean engine result does not fully resolve the behavioral concerns.
What We Detected
None of 75 antivirus engines flagged the JAR, and all 17 reporting tier-1 engines returned no detection. No matching malware family, researcher YARA rule, or external malware-feed record was found.
Threat Behavior
One completed sandbox run produced no malicious sandbox verdict, but it mapped activity to T1055 (Process Injection), T1543.002, and T1562.001. The process-injection heuristic explicitly notes that the available evidence does not establish the exact injection method or intent. The one observed domain was fully checked against the host cache and had no malicious or suspicious classification. Nine dropped children were inspected without a confirmed harmful result, although their individual verdicts remain unknown.
What To Do Now
Keep endpoint protection enabled and avoid running the JAR on a primary system unless its source and expected purpose are verified. If execution is necessary, use an isolated environment and obtain a fresh scan after vendors have had more time to assess this newly observed file.
Where this verdict could be wrong3 caveats
- MalwareTips.Synth.ProcessInjection fired at high severity for T1055, but its own evidence states that the mapping does not prove an injection method or malicious intent.
- The file was first submitted one day ago and similarHashes contains no prior matches, so reputation and history are still limited.
- All nine inspected dropped children have unknown verdicts, preventing them from serving as affirmative benign evidence.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines reported a detection.
- 17 tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false in one completed sandbox.
- The fully covered contacted host had no malicious or suspicious cache classification.
- No malicious dropped child or external-intelligence match was found.
- Runtime mappings include T1055, T1543.002, and T1562.001.
- MalwareTips.Synth.ProcessInjection fired at high severity.
- The sample was first observed only one day ago.
- All nine dropped-child verdicts remain unknown.
- No similar-hash history is available.
Do not run this newly observed JAR on a production or personal system until its origin and purpose are verified. Keep security protection enabled and rescan it after additional reputation develops.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 2 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 16MITRE ATT&CK techniques
- 15spawned processes
- 2network contacts
- 15filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Created or modified a system service, which can keep code running.
High concern: Attempted to impair or bypass security controls.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Transferred a file over the network; malware can use this to fetch additional payloads.
Moderate concern: Checks which security software you have installed.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
DupeMod.jar
5a052f7071b9e66a6f73473244f9b632c19885f9f73fb5871c364731ddecc306
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
5144
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5144
04Isolated runtime analysis - Written fileObserved
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
atm.teams.mira.tm.svc.cloud.microsoft
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- atm.teams.mira.tm.svc.cloud.microsoft
- 162.159.36.2
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5144
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
- C:\ProgramData\Oracle\Java\.oracle_jre_usage\17dfc292991c8786.timestamp
- C:\Users\user\AppData\Local\Temp\hsperfdata_user
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6552
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\3336
- /tmp/hsperfdata_root/3566
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- cef8bf0347c1bf3cc59f…338600Never scannednever seen before
- 96a8350c4d0703a405be…31374eNever scannednever seen before
- eeb8f8a5d8d5c7c158b9…3703e0Never scannednever seen before
- a325ff5f0b60ba1ff965…ecdf8cNever scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 61625fd8b084f70f242d…55abd2Never scannednever seen before
- 50c82f36208ed8040447…2d7843Never scannednever seen before
- 8e8711854186c68e2368…4a3c7cNever scannednever seen before
- 759aafcfa2395ce1b800…2af0f7Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 5sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 7 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: DupeMod.jar — 5a052f7071b9e66a6f73473244f9b632c19885f9f73fb5871c364731ddecc306
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\system32\icacls.exe C:\ProgramData\Oracle\Java\.oracle_jre_usage /grant "everyone":(OI)(CI)M
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: 5144 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5144
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: atm.teams.mira.tm.svc.cloud.microsoft — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
Evidence"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- DupeMod.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 897.5 KB
- Last analyzed
- Oct 5, 2026, 6:21 AM UTC
5a052f7071b9e66a6f73473244f9b632c19885f9f73fb5871c364731ddecc306Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this Java file and use a fresh copy from a trusted source. Get a fresh copy from the publisher's official site and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is DupeMod.jar safe, or is it malware?
What is DupeMod.jar?
How many antivirus engines detected DupeMod.jar?
What should I do if I already opened or ran DupeMod.jar?
How do I remove DupeMod.jar?
What is the SHA-256 hash of DupeMod.jar?
How up to date is this analysis of DupeMod.jar?
Community
Member reviews and reports for this exact file hash.