File scan report
Verdict Suspicious
Is catppuccin- addon- 2. 3. 0+ mc1. 21. 11. jar safe? Treat it as suspicious.
No antivirus engine detected this JAR, but one conflicting sandbox verdict and unconfirmed and mappings justify caution pending source verification.
Read the whole reasonShow less
Why Suspicious? One sandbox test run rated it malicious while another found nothing; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 66 flagged
- Flagged 0
- No detection 66
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 18d ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 66 antivirus engines that checked it flagged the JAR, and no malware family or malicious child was identified. However, one of two sandbox runs raised an alert and mapped possible process injection and service activity, while the other run was clean; those conflicting results prevent an unqualified benign assessment.
The strongest benign indicator is that none of the 66 antivirus engines that checked it flagged the file, including all 17 major contributors represented in the results. Evidence from the test run is inconsistent: one sandbox labeled the execution malicious, while another returned clean. and were mapped, but no injected target process, persistence artifact, malicious host contact, or confirmed malicious child supports those mappings. The seven dropped files lack saved verdicts, so they cannot be treated as either harmful or cleared. No malware-specific YARA rules or named family evidence corroborate the alert, making a sandbox false positive plausible but not proven.
What We Detected
None of the 66 antivirus engines that checked it flagged the JAR, and there was no named malware-family consensus. Research feeds also supplied no malware-specific YARA match or known-family identification.
Threat Behavior
Two sandbox runs disagreed: one produced a malware/trojan alert and the other returned clean. Runtime mappings included T1055 and T1543.002, but no target appeared in the injected-process list and no persistence indicator was recorded. Seven files it created were observed, but their saved verdicts are unavailable; they therefore provide no evidence in either direction. No complete contacted-host reputation check is available, although the recorded runs listed no sample network contacts.
What To Do Now
Verify the SHA-256 against the add-on's official distribution channel before installing it. If the origin cannot be confirmed, test it only in an isolated Minecraft profile or disposable environment while keeping security software enabled.
Where this verdict could be wrong3 caveats
- One sandbox produced a malware/trojan verdict and mapped plus T1543.002, which warrants caution despite the absence of antivirus detections.
- The file was first observed on Oct 8, 2026, so its reputation and prevalence history remain limited.
- No complete contacted-host reputation result is available, although the completed runs recorded no sample contacts.
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 66 antivirus engines that checked it flagged the file.
- All 17 major contributors represented in the results reported no detection.
- The second sandbox run returned clean.
- No malicious file it created was identified.
- No malware-specific research rule or named threat family matched.
- One of two sandbox runs generated a malware/trojan alert.
- The test run mapped possible process injection and service-related activity, although neither was concretely confirmed.
- The file is recently observed and has only modest submission history.
- Seven dropped files do not yet have saved classifications.
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; 1 test environment rated what it did as risky.
Test run summary
Capture complete- 16sandbox rule tags
- 3spawned processes
- 0network contacts
- 14filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.
Not confirmed: A sandbox rule tagged this run as creating a service; no new service was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
catppuccin-addon-2.3.0+mc1.21.11.jar
08b1dd9b4fb33bad11da3619b8b68fc4068a03ac6830ca733522a61194a5be58
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
javaw.exe
"C:\Program Files\Java\jre-1.8\bin\javaw.exe" -jar "C:\Users\<USER>\Desktop\sample.jar"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\SysWOW64\cmd.exe C:\Windows\system32\cmd.exe /c ""C:\Program Files\Java\jre1.8.0_441\bin\java.exe" -jar "C:\Users\user\Desktop\runtime.jar""
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
1728
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\1728
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 16 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 66 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
- Oct 13, 2026, 6:47 AM UTC
- SHA-256
08b1dd9b4fb33bad11da3619b8b68fc4068a03ac6830ca733522a61194a5be58- SHA-1
5b775fecf874ef11c19935ef5a294e571b78e399- MD5
2bf4f73c62c4d5fa225b41b3f0a91450
About this file
catppuccin-addon-2.3.0+mc1.21.11.jar is a JAR file of 429.1 kB.
- Type and size
- JAR · 429.1 kB
- Signer
- Not applicable
- First seen
- Oct 8, 2026On VirusTotal.
- Submitted by
- 6 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75), 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 catppuccin-addon-2.3.0+mc1.21.11.jar safe, or is it malware?
What is catppuccin-addon-2.3.0+mc1.21.11.jar?
How many antivirus engines detected catppuccin-addon-2.3.0+mc1.21.11.jar?
I already downloaded and opened or ran catppuccin-addon-2.3.0+mc1.21.11.jar — what should I do?
What is the SHA-256 hash of catppuccin-addon-2.3.0+mc1.21.11.jar?
How up to date is this analysis of catppuccin-addon-2.3.0+mc1.21.11.jar?
Community
Member reviews and reports for this exact file hash.