Is DrAyriAddons-1.1.1.jar safe?
Only Fortinet detected this JAR, while concerning technique mappings lack corroboration from the completed sandbox, contacted-host check, child inspection, or external intelligence.
Fortinet was the only one of 75 engines to flag the JAR, using a generic Java Agent label. The runtime record includes three concerning technique mappings, but the completed sandbox did not issue a malware finding, both contacted domains passed the available reputation check, and no malicious child or external-intelligence match was found.
bac6bf121034138c75…783a237312d935Recommended 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.
Fortinet was the only one of 75 engines to flag the JAR, using a generic Java Agent label. The runtime record includes three concerning technique mappings, but the completed sandbox did not issue a malware finding, both contacted domains passed the available reputation check, and no malicious child or external-intelligence match was found.
The antivirus evidence is weakly conflicting: Fortinet produced the only detection among 75 engines, while 16 other tier-1 engines reported no detection. Runtime analysis mapped activity to T1055, T1543.002, and T1562.001, which warrants caution, but the mapping does not establish malicious intent or a specific implementation. The sole completed sandbox returned a clean result and recorded no persistence indicators. Reputation checks covered both observed domains and found neither malicious nor suspicious entries, while inspection found no malicious child among nine hashes, although their individual dispositions remain unknown. With no family consensus, researcher-rule match, or known-malware intelligence hit, the evidence is insufficient for a definitive malware attribution.
What We Detected
Fortinet was the only one of 75 engines to flag the JAR, labeling it Java/Agent.AA!tr. No tier-1 family consensus formed, and 16 other tier-1 engines reported no detection. Independent intelligence checks produced no known-malware or researcher-rule match.
Threat Behavior
The completed runtime record mapped activity to T1055, T1543.002, and T1562.001. These mappings can represent process injection, service modification, and impairment of defenses, but the saved evidence does not prove the exact methods or intent. The sandbox itself returned a clean result and recorded no persistence indicators. Both observed domains were covered by the host-reputation check, with no malicious or suspicious entries, and none of nine inspected child hashes was identified as malicious; however, each child's individual disposition remains unknown.
What To Do Now
Keep endpoint protection enabled and obtain the JAR only from the project's official distribution channel. If its origin or expected functionality cannot be verified, avoid running it on a production or personal system and use an isolated test environment for further examination.
Where this verdict could be wrong3 caveats
- Fortinet is a tier-1 engine and labeled the sample Java/Agent.AA!tr, so its isolated detection carries more weight than a low-trust heuristic alert.
- The runtime mapping includes T1055, T1543.002, and T1562.001, which can correspond to process injection, service modification, and impairment of defenses.
- All nine inspected child hashes have unknown individual verdicts; hasMaliciousChild=false therefore provides limited reassurance rather than affirmative benign classification.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/75 engines detected the file
- No tier-1 family consensus
- The completed sandbox returned a clean result
- Both contacted domains had no malicious or suspicious reputation entry
- No malicious child or external-intelligence match was found
- Fortinet tier-1 detection: Java/Agent.AA!tr
- Runtime technique mapping includes T1055 process injection
- Runtime technique mapping includes T1543.002 service modification
- Runtime technique mapping includes T1562.001 impairment of defenses
- Nine dropped child hashes have unknown individual verdicts
- JAR signing is not applicable, leaving no publisher identity evidence
Verify the file against the project's official release source and checksum before use. Keep security protection enabled, and do not run it on a sensitive system if provenance cannot be established.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Complete2 contacted hosts were cross-checked.
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
- 15MITRE ATT&CK techniques
- 15spawned processes
- 2network contacts
- 14filesystem & 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: 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.
Note: Collects details about your system.
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
DrAyriAddons-1.1.1.jar
bac6bf121034138c753037c1828755a76cec9b639d305dce2f783a237312d935
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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
2676
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2676
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
eip-terr-na.cdp1.digicert.com.akahost.net
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
nexusrules.officeapps.live.com
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.
- eip-terr-na.cdp1.digicert.com.akahost.net
- nexusrules.officeapps.live.com
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2676
- 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\7056
- /tmp/hsperfdata_root/3545
Files this sample writes at runtime
This file drops 9 children at runtime. None are currently flagged malicious in our cache.
- de81e2981b8435b55a94…4e4a52Never scannednever seen before
- d7f4bf6a26b6a1150692…f1a14eNever scannednever seen before
- 055071b81dc8b648175d…20df88Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never 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
- 1 / 75engines flagged
- 44sources 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
1 of 75 antivirus engines flagged the file, including Fortinet.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 46 times from 44 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: DrAyriAddons-1.1.1.jar — bac6bf121034138c753037c1828755a76cec9b639d305dce2f783a237312d935
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\download.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: 2676 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2676
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: eip-terr-na.cdp1.digicert.com.akahost.net — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: nexusrules.officeapps.live.com — 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\download.jar"
1 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
- DrAyriAddons-1.1.1.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 164.4 KB
- Last analyzed
- Sep 26, 2026, 12:33 AM UTC
bac6bf121034138c753037c1828755a76cec9b639d305dce2f783a237312d935Safety & 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 DrAyriAddons-1.1.1.jar safe, or is it malware?
What is DrAyriAddons-1.1.1.jar?
How many antivirus engines detected DrAyriAddons-1.1.1.jar?
What should I do if I already opened or ran DrAyriAddons-1.1.1.jar?
How do I remove DrAyriAddons-1.1.1.jar?
What is the SHA-256 hash of DrAyriAddons-1.1.1.jar?
How up to date is this analysis of DrAyriAddons-1.1.1.jar?
Community
Member reviews and reports for this exact file hash.