Is swemcull-1.20.1-1.0.4.jar safe?
No antivirus engine detected this JAR, and its concerning behavioral mappings lack sandbox, child-file, network, or external-intelligence corroboration.
The file received no detections from 75 antivirus engines, including 16 tier-1 engines, and the completed sandbox did not issue a malware verdict. Three offensive-technique mappings warrant caution, but no malicious child or external-intelligence match corroborates them; the eight child files remain unclassified.
fb176adfd8e56b0307…a3e8fcd4e8ac9bRecommended 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.
The file received no detections from 75 antivirus engines, including 16 tier-1 engines, and the completed sandbox did not issue a malware verdict. Three offensive-technique mappings warrant caution, but no malicious child or external-intelligence match corroborates them; the eight child files remain unclassified.
No engine among 75 flagged the JAR, and 16 tier-1 engines reported no detection. One sandbox run mapped activity to T1055, T1543.002, and T1562.001, but it produced no malware verdict and observed no network contacts. None of eight inspected child hashes was identified as malicious, although every child remains unclassified rather than confirmed benign. Research intelligence returned no CIRCL, MalwareBazaar, or YARAify match. Because the host-reputation cross-check was not completed or saved, no complete network-reputation conclusion is available.
What We Detected
None of 75 antivirus engines flagged the JAR. Sixteen tier-1 engines reported no detection, including Avast, BitDefender, ESET-NOD32, Kaspersky, and Microsoft. CIRCL, MalwareBazaar, and YARAify supplied no matching intelligence.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1543.002, and T1562.001. These mappings can be associated with process injection, service modification, and security-control impairment, but the sandbox issued no malware verdict and recorded no contacted domains, IP addresses, or URLs. Eight child hashes were inspected without a malicious result, though all eight remain unclassified. A complete contacted-host reputation result is unavailable because that cross-check was not saved.
What To Do Now
Keep endpoint protection enabled and obtain the JAR from its official project or distribution channel. If its origin is uncertain, verify its hash or release signature against the publisher's release information before running it.
Where this verdict could be wrong3 caveats
- The runtime mapping includes T1055, T1543.002, and T1562.001, which can represent process injection, service modification, and impairment of defenses.
- All 8 dropped children have unknown verdicts, so droppedChildren.hasMaliciousChild=false does not establish that those files are benign.
- contactedHosts=null means no saved 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.
- 0/75 antivirus engines reported a malicious or suspicious detection.
- engines.tier1ReportedClean=16 and engines.tier1Malicious=0.
- behaviour.hasMaliciousSandboxVerdict=false.
- droppedChildren.hasMaliciousChild=false.
- YARAify, MalwareBazaar, and CIRCL returned no hits.
- Runtime evidence mapped activity to T1055, T1543.002, and T1562.001.
- All 8 dropped children remain unclassified.
- contactedHosts=null leaves host-reputation coverage incomplete.
- The sample was first submitted 19 days ago.
Use the file only if it came from the expected official source, and verify its hash against the publisher's release. Keep antivirus and endpoint protection enabled while testing it.
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
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
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
- 0network contacts
- 15filesystem & 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
swemcull-1.20.1-1.0.4.jar
fb176adfd8e56b03078027591f1213bf4a2de97ab8f5fbba68a3e8fcd4e8ac9b
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
5136
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5136
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>\5136
- 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\6524
- C:\Users\user\AppData\Local\Temp\hsperfdata_user\2976
- /tmp/hsperfdata_root/3567
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- d9b3be18e3662365aab7…657696Never scannednever seen before
- 33b0a19bd2f7d57e01e8…701934Never scannednever seen before
- ae87d23b6cb52ccc5b3b…e8c8e7Never 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
- 10sources 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 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 03
The hash has been submitted 10 times from 10 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: swemcull-1.20.1-1.0.4.jar — fb176adfd8e56b03078027591f1213bf4a2de97ab8f5fbba68a3e8fcd4e8ac9b
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: 5136 — C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\5136
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.
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
- swemcull-1.20.1-1.0.4.jar
- Format
- JAR
- Code signing
- Not applicable to this file type
- Size
- 275.1 KB
- Last analyzed
- Sep 9, 2026, 4:41 PM UTC
fb176adfd8e56b03078027591f1213bf4a2de97ab8f5fbba68a3e8fcd4e8ac9bSafety & 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 swemcull-1.20.1-1.0.4.jar safe?
What is swemcull-1.20.1-1.0.4.jar?
How many antivirus engines detected swemcull-1.20.1-1.0.4.jar?
What is the SHA-256 hash of swemcull-1.20.1-1.0.4.jar?
Is it safe to open or run swemcull-1.20.1-1.0.4.jar?
How up to date is this analysis of swemcull-1.20.1-1.0.4.jar?
Community
Member reviews and reports for this exact file hash.