The LoadModer team takes the security of our application, user environments, and Minecraft instances seriously.
| Version | Supported |
|---|---|
2.x.x |
✅ |
< 2.0 |
❌ |
If you discover a security vulnerability within LoadModer, please do not disclose it publicly via GitHub Issues.
Instead, please report security issues responsibly via:
-
GitHub Private Security Advisory:
Navigate to the Security Advisories tab and submit a private report. -
Direct Contact:
Send an email with the subject[SECURITY] LoadModer Vulnerability Reportto the repository maintainer.
- A clear description of the vulnerability.
- Steps to reproduce or proof-of-concept (PoC).
- Impact assessment (e.g., path traversal, SSRF, arbitrary file write).
- Affected versions or platforms (Windows, Linux, macOS).
- Initial Acknowledgment: Within 48 hours.
- Triage & Reproduction: Within 5 business days.
- Fix & Advisory Release: Coordinated with the reporter prior to public disclosure.
LoadModer enforces strict defensive controls:
- Zip-Slip & Path Traversal Prevention: Remote modpack archive paths are sanitized against traversal attacks.
- SSRF Mitigation: Download targets are strictly restricted to trusted Modrinth CDN and Mojang domain endpoints.
- Streaming Integrity Verification: Remote files are downloaded to temporary
.partbuffers and verified against SHA-512 checksums before moving to final destinations. - Atomic State Persistence: All critical states are written using
write-file-atomicto prevent partial corruption.