File scan report
Verdict Safe
Is genyo-
None of the 65 antivirus engines that checked it flagged this Java add-on archive, and the sandbox runs showed only the Java runtime starting it, with no high-risk techniques.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
This Java add-on shows no signs of malicious activity; use it if it came from the official source of the software it extends, and keep your security software enabled.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the project's own website.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
0 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The sandbox runs show the Java runtime launching it and writing routine runtime files. No injection target and no network activity of its own were recorded. It has been seen from 12 sources over about two months.
None of the 65 antivirus engines that checked it flagged the file, and all 18 major antivirus engines returned clean results. The sandbox runs recorded only the Java runtime processes needed to run the archive, plus standard JVM bookkeeping files. The behaviour mappings are techniques common in legitimate software, and the two higher-risk labels were mapped without any matching artefact or targeted process. The only network contact was the analysis machine's own background traffic. With no brand impersonation, no hostile dropped file and moderate prevalence, nothing in the evidence points to harmful intent.
What We Detected
None of the 65 antivirus engines that checked it flagged this Java archive. All 18 major antivirus engines, including Kaspersky, ESET, Microsoft and BitDefender, reported it clean. It has been submitted from 12 sources since it first appeared on Aug 23, 2026.
Threat Behavior
In the sandbox runs, the archive was started by the Java runtime. It wrote only ordinary JVM performance and usage files. No process injection target, persistence, registry changes or network contact of its own were recorded; the single contact observed was the analysis machine's background traffic. Some behaviour labels appear by default on many clean programs and were not backed by any matching activity. We do not have a complete reputation check for contacted hosts.
What To Do Now
If you obtained this add-on from the developer or the official distribution channel of the software it extends, it can be used normally. Keep your antivirus enabled and download future updates from the same trusted source.
Where this verdict could be wrong1 caveat
- Java archives can fetch further code when it ran, and no complete host-reputation result is available for this file. However, the sandbox recorded no network contact of the sample's own.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 65 antivirus engines that checked it flagged the file, including all major antivirus engines
- The sandbox showed only the Java runtime running the archive, with no high-risk techniques
- No process injection target, persistence or network activity of the sample's own was recorded
- Seen from 12 independent sources over roughly two months
6 sources checked · 5 complete · 1 not needed or not applicable. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 15sandbox rule tags
- 3spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
Includes 15 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 65 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Sep 8, 2026, 3:39 PM UTC
- SHA-256
6a7bf8c5dc74a58a4aec8ff7924a72d6e7b3f4f4f5cc14e9ab0b5fb5982d911a- SHA-1
7789ceabcc3bf12af42cccb2e786543eed8558b0- MD5
467f63c544400f06b6be38ae0ea494bd
About this file
genyo-addon-2.2.2.jar is a JAR file of 4.8 MB.
- Type and size
- JAR · 4.8 MB
- Signer
- Not applicable
- First seen
- Aug 23, 2026On VirusTotal.
- Submitted by
- 12 distinct sources
First scanned Updated
Verdict history
- Suspicious
- Safeafter a re-check of the saved evidence
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (74), 1 matched signature rule and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is genyo-addon-2.2.2.jar safe?
What is genyo-addon-2.2.2.jar?
How many antivirus engines detected genyo-addon-2.2.2.jar?
What is the SHA-256 hash of genyo-addon-2.2.2.jar?
Is it safe to open or run genyo-addon-2.2.2.jar?
How up to date is this analysis of genyo-addon-2.2.2.jar?
Community
Member reviews and reports for this exact file hash.