Solver

Solver 0.9.0

Solver can now verify its own jar and scan for known-malware plugins. Both static, signed, and cached — no dynamic backend involved yet.

FyrxLab Backend (Beta): Solver can now verify its own jar and scan for known-malware plugins. Both static, signed, and cached — no dynamic backend involved yet.

Highlights

• New: build integrity + malware scanning — Solver verifies its own jar against a signed hash published by FyrxLab, and scans every other .jar in plugins/ against a list of known-malware hashes. Both are static, signed files cached locally and refreshed only every so often, not a live backend. Check anytime with /solver integrity, or force an immediate check with /solver integrity rescan.
• Optional: Modrinth cross-check for unflagged plugins — plugins that don't match the malware list can also be checked against Modrinth's public hash database, purely informational (never a red flag on its own — plenty of legitimate plugins simply aren't on Modrinth).
• New: Java agent detection — Solver now warns at startup if a Java agent was attached to the server's JVM, since an agent can patch classes in memory (including this very integrity check) without ever touching the jar file on disk.
• Fixed: /solver rtp could occasionally teleport the person running the command to themselves instead of another player.

More details: docs.jeamcube.com/en/solver/changelog