Is casino_rig_1.21.10.jar safe?
No antivirus engine flagged the 46 kB JAR despite 74 total scans.
Zero malicious detections from 74 engines, medium prevalence, and a clean community annotation indicate the file is benign. Sandbox activity shows only ambient and two defensive techniques without malicious outcomes.
c53a27142a9e1b7ddf…97dfb834a0afd4Recommended next actions
Before opening or running
Open or run it only when its publisher and download source have been independently verified.
If you already opened or ran it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
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.
Zero malicious detections from 74 engines, medium prevalence, and a clean community annotation indicate the file is benign. Sandbox activity shows only ambient and two defensive techniques without malicious outcomes.
The complete absence of detections across tier-1, tier-2 and low-trust engines outweighs the two MITRE techniques observed in the sandbox. Medium prevalence and an explicit clean community report further support safety. No external-intel hits or dropped malicious children exist. The lack of a contacted-hosts cross-check is noted but does not alter the verdict given the other evidence.
What We Detected
74 engines scanned the 46 kB JAR; none returned a malicious or suspicious result. Sandbox execution recorded two MITRE techniques (T1543.002, T1562.001) and eight ambient ones, but produced no malicious verdict or dropped children.
Threat Behavior
The file writes temporary Java performance data and log files, adjusts permissions via icacls, and restarts the CUPS service on Linux. No C2 domains, persistence mechanisms, or malicious child files were observed.
What To Do Now
The file can be executed in a standard environment. Keep endpoint protection enabled and monitor for any unexpected outbound connections.
Where this verdict could be wrong2 caveats
- behaviour.offensiveTechniques include persistence and defense-evasion IDs that could indicate malicious intent, yet sandboxVerdicts and droppedChildren show no malicious outcome.
- contactedHosts is null, so no complete host-reputation cross-check is available.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero detections across 74 engines
- Medium prevalence with 53 submitters
- Explicit clean community annotation
The sample shows no malicious indicators; treat it as safe for normal use while retaining standard security controls.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 10MITRE ATT&CK techniques
- 15spawned processes
- 0network contacts
- 14filesystem & mutex artifacts
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
casino_rig_1.21.10.jar
c53a27142a9e1b7ddf5f9993b3bd13439969cc350275d5272b97dfb834a0afd4
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.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
5660
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5660
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
5 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.
- C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5660
- 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\6876
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\6548
- /tmp/hsperfdata_root/4970
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache.
- d8d86f10fa9bac5e50da…8a88daNever scannednever seen before
- 6b270f65a5f433d2ea56…019039Never scannednever seen before
- c1de3a9376fdaef0ba6a…308b70Never scannednever seen before
- d87c5f3cdfb5b7c0510e…1ade9eNever scannednever seen before
- 44a3bab2c338e3bca24c…d3b9e7Never scannednever seen before
- ac941ead01d5451a7a9f…253227Never scannednever seen before
- d997d4c933c09d2ff0cc…22626cNever 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.
- 0rule hits recorded
- 0 / 74engines flagged
- 53sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 03
The hash has been submitted 57 times from 53 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: casino_rig_1.21.10.jar — c53a27142a9e1b7ddf5f9993b3bd13439969cc350275d5272b97dfb834a0afd4
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Program Files\Java\jre-1.8\bin\java.exe" -jar "C:\Users\<USER>\Desktop\runtime.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: 5660 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5660
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: 3903daac9bc4a3b7.timestamp — C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 74 engines flagged this file
View all 74 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
- casino_rig_1.21.10.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 45.0 KB
- Last analyzed
- Jul 26, 2026, 6:06 AM UTC
c53a27142a9e1b7ddf5f9993b3bd13439969cc350275d5272b97dfb834a0afd4Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Open or run it only when its publisher and download source have been independently verified.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is casino_rig_1.21.10.jar safe?
What is casino_rig_1.21.10.jar?
How many antivirus engines detected casino_rig_1.21.10.jar?
What is the SHA-256 hash of casino_rig_1.21.10.jar?
Is it safe to open or run casino_rig_1.21.10.jar?
How up to date is this analysis of casino_rig_1.21.10.jar?
Community
Member reviews and reports for this exact file hash.