Detection
Minecraft session token and launcher account theft
A client mod runs inside the game process, so it can ask Minecraft for your session and read the launcher's account files like any other file. The harm starts when that data leaves your computer.
What the behaviour looks like
The classic chain is: get the game client, read its session object, take the access token, UUID and name, build a small JSON body, and send it to a server or webhook. Each step is an ordinary API call. Hiding the names (Yarn, Mojang, intermediary or SRG) only changes the spelling, not the structure.
Rules in this family
mc.session-token.access: the access token is read from the session.mc.session-token.network: a session value reaches a network call.mc.session-token.reflection: the session is reached through reflection or hidden names.mc.session.mixin: a mixin hooks session handling.mc.authlib.join-server: the join-server call is used with a stolen token.mc.launcher-accounts.path: a path to a launcher account file is built.mc.launcher-accounts.read: that account file is actually read.
What is not suspicious
Many clean mods show your username in a menu or a chat message. Reading getUsername() and drawing it is normal. The scanner raises its concern when the token or account file is paired with network use.
Related reading
How Minecraft token stealers work, LoaderClient and what to do if you ran one.
One finding is a lead, not a verdict. RatOrNot combines these signals and follows the call path from the mod entrypoint, so a mod that reads a value to display it scores very differently from one that sends it away. See false positives in jar scanners, or scan a mod now.
