Skip to content

Launcher security

Installer signature

  1. Right-click the file
  2. Properties
  3. Digital Signatures

Code and build

  1. Kodmillida/launcher
  2. ModpackGitHub Actions
  3. ReleaseGitHub build attestation

What is sent to the server

  • System and launcher version
  • CPU, memory, graphics card
  • Game launches and crashes
  • Screens and button clicks
  • Linked to your Millida account if you are signed in

Not sent

  • Passwords and tokens
  • Your folder name on disk
  • Chat and search text
Ustawienia Konto Usage statistics

What the launcher does not do

  • Never sees your Microsoft password
  • Never hands your token to Millida
  • No mining
  • Does not read browser data
  • Interface has no disk or shell access

Antivirus warning

  1. Blue window: “More info” › “Run anyway”
  2. Defender removed the file: “Protection history” › “Allow on device”, then download again
  3. Third-party antivirus: add the installer to exclusions

Found a problem

The file is new

SmartScreen uznaje plik za nieznany, dopóki nie pobiorą go tysiące osób. Każda nowa wersja zaczyna licznik od zera, a potem ostrzeżenie znika samo.

A launcher behaves like malware

It downloads files from the internet, unpacks archives, installs Java and runs it with its own arguments. Antivirus machine learning reacts to exactly this behavior, so every Minecraft launcher falls under suspicion.

A signature does not skip the check

The installer is signed with an EV certificate and Windows shows the publisher by name. Trust builds on the file itself, not only on the certificate.