Threat LensFile scan report

Is glazed-26.1.2-n-17.1.jar safe?

Verdict
Safe

No antivirus engine detected the JAR, and its sandbox run produced no malicious conclusion, although several offensive MITRE technique mappings warrant ordinary caution.

None of 75 antivirus engines flagged this JAR, including all 17 tier-1 engines, and the completed sandbox run did not produce a malicious conclusion. Three offensive MITRE mappings are the main concern, but they lack corroboration from engine detections, known-malware intelligence, network activity, or malicious dropped children.

Open or run with normal care

Use the file only from a trusted release source and verify its SHA-256 against the publisher's published checksum when available. Keep endpoint protection enabled and isolate it if the origin cannot be confirmed.

Read the full analysis
Saved file evidenceAntivirus consensus
0of 75 flagged
Flagged 0No detection 75
Digital specimenglazed-26.1.2-n-17.1.jar3d3f6c04cbd36b9e15…983cb5691d77ec
Size1020.8 KB
Code signingNot applicable
SandboxRuntime complete
First seen2mo ago
Evidence3 priority signals
0 of 75 antivirus engines flagged the file.

Recommended next actions

01

Before opening or running

Open or run it only when its publisher and download source have been independently verified.

02

If you already opened or ran it

Keep normal device protection enabled and stop if the file behaves unexpectedly.

Chapter 02

Intelligence

The saved assessment, checked against the scan evidence and recorded coverage.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.

82%Confidence
High
Analyst conclusion

None of 75 antivirus engines flagged this JAR, including all 17 tier-1 engines, and the completed sandbox run did not produce a malicious conclusion. Three offensive MITRE mappings are the main concern, but they lack corroboration from engine detections, known-malware intelligence, network activity, or malicious dropped children.

Where this verdict could be wrong3 caveats
  • The runtime mapping includes T1055 process injection, T1543.002 service execution, and T1562.001 defense impairment; these capabilities deserve caution even though the sandbox did not issue a malicious verdict.
  • All nine dropped children have unknown individual verdicts, so droppedChildren.hasMaliciousChild=false does not establish that every child is benign.
  • contactedHosts=null means no complete host-reputation result 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.

Recommended action

Use the file only from a trusted release source and verify its SHA-256 against the publisher's published checksum when available. Keep endpoint protection enabled and isolate it if the origin cannot be confirmed.

Scan transparency

Coverage & freshness

4 of 5 complete

Complete means the check returned a usable result. It does not mean the file is safe.

  • Antivirus

    Complete

    0 of 75 engines flagged the file.

  • Sandbox

    Complete

    1 isolated runtime environment contributed observations.

  • Network

    Not run

    No contacted-host reputation check is recorded.

    No timestamp recorded
  • YARA

    Complete

    1 signature or behavior rule matched.

  • External intel

    Complete

    3 of 3 independent reference sources completed.

Chapter 03

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
Chapter 04

Detection & Forensics

Consensus, attribution, signatures, code structure, prevalence, and identity.

Chapter 05

Safety & 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.

  1. Recovery step 01

    Open or run it only when its publisher and download source have been independently verified.

  2. Recovery step 02

    A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.

  3. 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.

6 evidence-based answers
Is glazed-26.1.2-n-17.1.jar safe?
Evidence-based answer
glazed-26.1.2-n-17.1.jar appears safe. 0 of 75 antivirus engines flagged it. Open or run it only when its publisher and download source have been independently verified.
What is glazed-26.1.2-n-17.1.jar?
Evidence-based answer
glazed-26.1.2-n-17.1.jar is a Java application or archive, about 1021 KB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
How many antivirus engines detected glazed-26.1.2-n-17.1.jar?
Evidence-based answer
None — 0 of 75 antivirus engines flagged glazed-26.1.2-n-17.1.jar. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
What is the SHA-256 hash of glazed-26.1.2-n-17.1.jar?
Evidence-based answer
The SHA-256 hash of glazed-26.1.2-n-17.1.jar is 3d3f6c04cbd36b9e156b9a9fa66e160e326739adf6301278e2983cb5691d77ec, and its MD5 is 9c3c33adaecad4e170c88b8208616bce. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
Is it safe to open or run glazed-26.1.2-n-17.1.jar?
Evidence-based answer
Based on the recorded evidence, glazed-26.1.2-n-17.1.jar has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
How up to date is this analysis of glazed-26.1.2-n-17.1.jar?
Evidence-based answer
This report reflects the scan run on October 1, 2026. Because a file's hash never changes, the identity of glazed-26.1.2-n-17.1.jar is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Chapter 06

Community

Member reviews and reports for this exact file hash.

The raw file is processed temporarily and is not retained after processing. Its hash and report are public and permanent, so the next person who checks the same file gets an instant answer. Unknown files may be submitted to VirusTotal for analysis. If you ran this file on your computer and are worried, scan your system with an up-to-date antivirus and change critical passwords from a different device.