[!WARNING]
Final verdict available at the end of this report.
The scanner examined 19,182 classes inside the JAR and was able to decompile every one of them. Only 25 classes (0.13 %) triggered decompiler anomalies, mostly due to very large or complex methods – a common situation for performance‑critical code and not a sign of hidden malware.
The report flagged 1,088 classes (≈5.7 %) as “suspicious”. Most of these belong to well‑known libraries that the server bundles (e.g., Netty, Gson, Guava, bStats, Sentry, Mojang authentication). The scanner also detected many outbound‑connection indicators (HTTP URLs, socket usage) and file‑access indicators, but the destinations are official Minecraft‑related services and typical update/telemetry endpoints.
Because the scanner works statically, it cannot see runtime behaviour, but the evidence shows that the majority of flagged items are normal for a Minecraft server implementation rather than malicious code.
papermc.io, bstats.org, sessionserver.mojang.com, and sentry.io for updates, metrics, and authentication.No high‑signal malicious behavior was detected. The scanner did not find code that explicitly steals credentials, writes hidden files, downloads unknown payloads, or executes arbitrary commands beyond the server’s normal startup sequence.
The evidence does not match a Remote Access Trojan. While the JAR can open network sockets (required for a Minecraft server) and uses reflection/class‑loader APIs (common for plugin loading), there is no persistent back‑door or remote‑control logic.
| Class | Severity | Behavior | Evidence |
|---|---|---|---|
com.universeprojects.bootstrap.BootstrapMain |
Medium | Starts the server, builds classpath, downloads required libraries, checks for updates | process_builder_api, file_access_api, hard‑coded URLs to Maven repos |
com.universeprojects.command.subcommands.ReloadSubCommand |
Low | Reads configuration files | java_io_file_api |
com.universeprojects.config.UniverseConfig |
Low | Reads/writes config, sends telemetry to sentry.io |
http_url_literal, file_access_api |
purpur.PurpurConfig |
Low | Reads server config, contacts purpurmc.org for docs |
http_url_literal, file_access_api |
| Class | Severity | Behavior | Evidence |
|---|---|---|---|
com.destroystokyo.paper.Metrics (bStats) |
Low | Sends anonymous usage statistics | http_url_literal, java_net_url_api |
com.mojang.authlib.* |
Low | Authenticates players with Mojang/Yggdrasil | http_url_literal, url_connection_api |
io.netty.* |
Low | Handles network sockets for the server | socket_api |
org.bstats.* |
Low | Metrics collection | http_url_literal |
com.google.gson.* |
Low | JSON parsing | No network activity |
org.slf4j.*, org.apache.commons.io.* |
Low | Logging and file utilities | file_access_api |
The JAR contacts the following domains (all official and expected for a Minecraft server):
papermc.io, repo.papermc.io – Paper server updates and Maven repositorybstats.org – Anonymous usage metricssessionserver.mojang.com, api.mojang.com, api.minecraftservices.com – Player authenticationsentry.io – Error reportingpurpurmc.org – Purpur configuration docsgithub.com – Version check for Paperrepo1.maven.org, repo.maven.apache.org – Dependency fetchinglogging.apache.org – Log4j configuration (legacy)All URLs are hard‑coded in the code and used for legitimate purposes such as update checks, telemetry, and authentication.
Yes. The JAR is a Minecraft server implementation (UniverseSpigot) built on top of Paper/Spigot. It contains the usual server core, networking stack, and optional telemetry libraries.
papermc.io, purpurmc.org, and GitHub for version information.sessionserver.mojang.com and related APIs.The scan did not reveal any truly dangerous behavior:
Static analysis can identify suspicious patterns but cannot guarantee runtime safety. It cannot see how the server behaves when loaded with plugins, nor can it detect malicious activity that only triggers under specific conditions. Always combine static results with good operational security (firewalls, regular updates, trusted plugins).
Yes, a JAR can embed malicious Java bytecode that runs when the JAR is executed. However, many JARs contain harmless code that merely performs legitimate functions.
Use a reputable static scanner (like the one that produced this report), verify the source, inspect the code or decompiled output if possible, and monitor its runtime behavior (network traffic, file access).
The scanner flags indicators such as remote command execution, hidden downloads, and suspicious network activity. It can highlight potential RAT‑like behavior, but final judgment requires context (e.g., whether the code belongs to the server core or a third‑party plugin).
Not necessarily. Some legitimate libraries use code generation or optimization that results in missing debug information. Persistent, heavy obfuscation combined with suspicious indicators may warrant deeper investigation.
Verdict: Mostly trust
Risk level: Low to Medium (mostly due to normal telemetry and update checks)
Confidence: High – the scan covered the entire JAR, and all suspicious findings are explainable as standard server functionality or known third‑party libraries.
Should I trust this JAR, and why?
UniverseSpigot‑1.21.11.jar is a standard Minecraft server build that includes typical networking, authentication, and telemetry components. The few flagged items are either part of its normal operation (update checks, metrics, file handling) or come from well‑known libraries. No evidence of hidden malware, credential theft, or remote‑control capabilities was found. Therefore, it can be used safely, though you may wish to disable optional telemetry if privacy is a concern.