Open a security timeline on a Tuesday and the headlines collapse into one sentence: someone put Discord tokens and Telegram sessions in the same shop. The citation people keep forwarding is not a new bug number against Discord’s servers. It is Flare researcher Sukant Kumar’s TWEAKOS write-up from 24 September 2026. The entry point was a Python paste on Pastebin. That paste exposed a hardcoded Telegram bot token and two administrator user ids. Following that bot token, the analysts found a second, larger program: intake, a ledger, a price list, and payment in Telegram Stars, all hanging off the same bot.

An earlier piece here asked who can still walk into the AI session in your browser after you change the password and MFA. That was a door card left behind after a web login finished. This piece switches to two chat accounts, and the question is narrower: after a Discord login token has already been read out of a local file, and Telegram has an extra session that never went through the official client, what do the two password changes you just made each leave behind. MyPassGen’s tools open without an account. They do not scan the disk, and they do not end a Discord or Telegram session for you.

Do this first

If you typed a phone number, an SMS login code, or a cloud password into a window that was not the official Telegram client, open Settings → Devices on a phone you have already used for a long time and end the row you do not recognize. On a device that just signed in, the client refuses to end older sessions right away. On Discord, the help center says changing the password logs out every device at once. Do not paste a token you are still using into chat as a test.

Two programs, one bot token

The report describes TWEAKOS as two Python programs written to run together. The first one targets Windows and stays inside the current user’s rights. It looks through the Discord stable client, the Discord public test build (PTB), and the local storage of Chrome’s default profile for strings that look like a login token. It then asks Discord’s current-user API about each candidate. Only a reply of HTTP 200 is sent onward, and that message also carries the username tag and the account id. The Chrome path searches .log and .ldb files in local storage. The report is explicit that this code leaves Chrome’s saved-password store alone, leaves cookies alone, and leaves the browser’s encryption keys alone.

The second program is a Telegram bot that stays up. It uses the same bot token and the same administrator ids, and it records victims, listings, buyers, orders, and administrator actions in one SQLite file, tweakos_data.db. The shop splits stock into telegram and discord, and it takes payment in Stars (currency code XTR). The listed price falls 5% for each day the item stays up, the discount stops at 70% (a floor of 30% of the original price), and the price stays at or above 1 Star. Flare calls “a stealer and a storefront inside the same bot process” the first case of that shape they have seen. That sentence judges this code. The report leaves the number of affected people blank.

Headcount and the way the program arrived are both left blank. The analysts did not confirm how the program reached a computer, and they did not confirm how many people ran it. They ran one read-only query with the bot token that the paste had exposed. At that moment they received no usable reply, and the related channel would not open. That observation covers the moment of the investigation: the exposed token and the channel were unusable then. It leaves earlier deliveries, and a later bot with a different token, outside what that query can show.

The two programs also fail to line up with each other. The bot tries to parse a Discord token out of messages that contain the uppercase word DISCORD and a Russian label for “token.” The first program sends a title that is only title-case Discord. A case-sensitive match therefore fails, and the discord-token column in the database can be empty. The report says this gap affects bookkeeping in the back office. The token can already be sitting in the administrator chat. An empty column is a ledger miss. The string can still have left the machine.

The Discord token sits in a local file

A Discord login token is the string the client uses to prove “this person is already signed in.” The password you type into the login box is a different secret. The password stays in your memory or in a password manager. The token is written into Discord’s local storage on this machine, and into Chrome’s default profile if you have signed in to Discord on the web. Someone who takes a string that already passed the check can use the account for as long as that string stays valid, without guessing the password.

The official line you can check sits in the help-center note on QR-code login: if you approved a login that was not yours, change the Discord password, and that change logs out every device, including the ones you never approved yourself. The path is User Settings → My Account → Change Password. When the account has multi-factor authentication on, the change asks for a code first. The help center ties “log out of all devices” to the password change. It does not offer a separate button that voids tokens and leaves the password where it is.

On the Discord side, then, the password change is what retires the door card. Flare’s advice points the same way: treat a token that already returned HTTP 200 as already sent out, change the password now, and turn on multi-factor authentication so the next password login has a second check. Multi-factor authentication guards the login box. The old string can still sit in someone else’s chat log. “They still have the characters” and “those characters still pass Discord’s current-user API” are two checks. After you change the password, the check you can do on the spot is whether another Discord window that was already open returns to the login page.

The local file is a third line. The program’s persistence stays inside the current user and does not ask for an administrator. The packaged executable copies itself into the current user’s Startup folder under the name SystemHelper.exe. If it runs as a script, it writes a value named SystemHelper under HKCU\Software\Microsoft\Windows\CurrentVersion\Run, pointing at the script path. Both entries are current-user only. A startup entry that is still there means the next sign-in can read a fresh token. Change the password first. Look at the startup entry second.

That scope is narrower than “every password saved in Chrome was taken.” The report limits the Chrome path to local storage in the default profile, matching the shape of a Discord token. The password store and cookies are outside this program’s read list. Saved logins for other sites belong to a different class of program. This TWEAKOS file list does not stand in for that check.

Telegram waits for the login code you type

On Telegram, the script performs a new login while you are sitting there. It asks for a phone number, sends a login code through Telethon, and then asks you for that code. When the account has a cloud password (two-step verification), it asks for the password once more, so this login can finish. After that it calls an API to read the cloud-password state. The report quotes a comment in the code: if no cloud password was set, the program generates a random string and puts it in the outgoing message, and the comment notes that this string was not technically set as the password, and that the session had already been taken. The code has no step that updates the password. If a cloud password was already set, the message is written as “password already exists, not modified.” The result is one more session. The password stays the value it already was.

That session lands in a .session file named after the phone number. Text and file go out as two sends: one message states the phone number and the status, and a second message sends the file as a document to the hardcoded administrators. Once the file is in their chat, they can keep using that login with Telethon. Changing the cloud password later in the official client leaves that file in their chat history.

Telegram’s own FAQ writes this as two steps. In the note on a stolen phone, Telegram first points you to Settings → Privacy and Security to turn on two-step verification, so a phone number by itself is not enough to sign in. It then points you, separately, to Settings → Devices (or Privacy and Security → Active Sessions) to end sessions on older devices. The two-step-verification note says that, once it is on, a new login needs the SMS code and this password. It does not say that a new cloud password signs other devices out. The lost-phone checklist lists “end the session” on its own line, which is how an existing device stays on the list after you set a new password.

The client adds a limit of its own. Telegram’s interface text says that, for security, you cannot end an older session from a device that just connected; use a device that signed in earlier, or wait a few hours. If you reinstalled Telegram only after the suspicious login, “end other sessions” on that new device can be greyed out. The password change can still have succeeded. End the row from a device you have stayed signed in on, or wait until the client allows it. The FAQ also says Telegram cannot stop a person who has your unlocked computer, or a person who can operate that machine. A dark window asking you for a login code sits inside that boundary.

Cloud chats also sync the words you type afterward. The FAQ says the same number can be signed in on many devices at once, and cloud chats sync across those devices. A session you have not ended yet can read plaintext you send in an ordinary chat, including a new password you send a colleague to “replace the old one.” A secret chat is a different object: it exists only on the device that created it, and it stays out of the cloud. An ordinary group and an ordinary private chat are not secret chats. Typing a new password into a Telegram cloud chat types it to every device still on the list.

A price list, and a bot that did not answer

The second program treats the taken accounts as inventory. After an item is listed, the price falls 5% a day, the discount stops at 70%, and the price stays at or above 1 Star. A buyer pays inside the same bot and, after the sale, receives a block of text with the account type, a login identifier, and a password or a token. The administrator receives the item id and the amount. That commercial shape is written in the code. It does not show that the shop was still taking orders while the investigation was running.

Flare names three things the investigation did not complete. A read-only query with the exposed bot token returned no usable reply from the bot. The related channel would not open. WindowsSecurityChecker.exe, named in the code, was not found alongside the source, so what that follow-up file actually does stays unconfirmed. The interface and the comments are in Russian. The report treats that as a sign the operating environment leans Russian, and it says that sign is not enough to assign the code to one person or one country. The Discord invite discord.gg/tweakos opened as an invalid invite at the time of the analysis.

One more script appears only when an administrator starts it by hand. It loops a window in the style of “this computer is locked” and leaves a Discord invite on screen. The script is generated per victim id, and the local copy is deleted after it is sent. The popup is there to pressure you. The script leaves the files on disk unencrypted. If that window is on your screen, disconnect the network, and from a clean device change the Discord password and end the Telegram sessions. Leave the invite in the window unanswered.

Put those gaps next to the capabilities the report does spell out, and the question in the title holds. The shop may already be unreachable. The Discord column in the database may be empty. The follow-up executable may never have shipped with the paste. A token and a .session file that already reached the administrator chat stay in that chat history when the bot later goes quiet. A password change and an ended session decide whether that string and that session can still sign in. They leave the file the other side already received where it is.

What each action still leaves

Read this table against an account you can throw away, not against the account you are on call with. Discord’s “change password” and Telegram’s “change password” are different controls. The rows below stay inside the official notes cited above and inside results the Flare report already states.

What you did Discord token Telegram session
Changed only the Discord password Official note: every device signs out, including logins you did not approve Leaves Telegram untouched
Turned on Discord multi-factor authentication only The next password login needs the code; a token already sent out is retired by the password change Leaves Telegram untouched
Changed only the Telegram cloud password Leaves Discord untouched A new login needs this password; the FAQ leaves existing devices on the list
Ended the Telegram session from a device you have used for a long time Leaves Discord untouched That authorization ends; the file can remain in the other chat, and it should no longer be able to sign in
Tapped “end other sessions” on a device you just installed Leaves Discord untouched The client can refuse, and it asks you to use an older device or to wait a few hours
SystemHelper.exe is still in the Startup folder The next sign-in can read a new token Typing a login code into that window again can mint another session

Keep the last row separate from the rows above it. Discord’s sign-out happens on the password change. The Telegram session ends from the device list, as its own step. A startup entry that is still there can ask for a login code the next time it runs. After you have looked at all three, the title has an answer: the old text can still sit in the other side’s chat; whether it can still sign in depends on whether Discord logged every device out, and on whether that Telegram row is gone from the device list.

Check it on the spot

These steps use your own account pages and the startup entries on this machine. They do not ask you to run a program from an unknown source. If the Discord check has to touch a real account, do it beside another client that is already open, and watch whether that client returns to the login page. For Telegram, use a phone you have stayed signed in on. Leave tokens, login codes, and the cloud password out of chat, tickets, and screenshots.

  1. Open Discord’s help-center note on changing a password, and finish User Settings → My Account → Change Password. A desktop or web client that was already open beside you should return to the login page. This step checks the official line “log out of all devices.” It skips digging the string out of local storage. If you do see that string, leave it uncopied.
  2. On Windows, look in the current user’s Startup folder for SystemHelper.exe. The path in Explorer’s address bar is %APPDATA%\Microsoft\Windows\Start Menu\Programs\Startup. Then look under the current user’s Run key for a value named SystemHelper. If either is present, finish the password change in the previous step, then remove the startup entry. If neither name is present, these two filenames from the report are absent on this machine. Other programs can still be there under other names.
  3. On the Telegram you have used for a long time, open Settings → Devices. Each row shows an app name, a rough place, and a time. End the row that is not yours. If the client says you cannot end an older session from a device that just connected, go back to the older phone, or wait as the prompt says. Signing in again and again on the new device is a poor way to push the old session off the list.
  4. Open Settings → Privacy and Security → Two-Step Verification and confirm that a new login asks for the cloud password. This step sits beside the device list. The FAQ writes the two as a sequence. A new password with the old row still listed leaves that older device in place.
  5. Before you send anything, look again at whether the device list still has a row you do not recognize. If it does, end that row first. Then send yourself a disposable test sentence in an ordinary cloud chat, for example orange-lake-7. Cloud chat syncs to every device you have not ended. After the sentence goes out, delete it from the chat, and remember that deleting your side leaves a copy the other side already received where it is.

After the first four steps you can answer the title in two parts. Another Discord client returned to the login page, so this password change signed devices out the way the help center describes. The unrecognized row disappeared from Telegram’s device list, so that session is no longer listed as active. If SystemHelper is still in the startup entries, the next sign-in can still read a new token. Keep the test sentence disposable. A real password does not belong in that chat.

How to hand a new password to a colleague

The new Discord password and the new Telegram cloud password are still credentials. Leave them out of cloud chat, out of a server channel, and out of a ticket that will be screenshotted. For a one-to-one handoff the other person needs right now, wrap the secret on this machine as a one-time link. MyPassGen’s one-time link opens without an account. The browser encrypts with AES-256-GCM. A single note caps at 32 KB. Reads default to 1 and cap at 10. Expiry can be 1 hour, 24 hours, 7 days, or count-only with no TTL. The server parks ciphertext only. The link looks like s.html?id=…#…. The key sits after #, and that fragment is not sent to the server with the HTTP request.

Split the channel. Discord, or the ticket, carries only the id and the sentence “key by phone.” A call, or an in-person handoff, carries only the slice after #. Either half alone stays unreadable. That split is a way to use the link. The create page still gives you one full URL, which is convenient when you want to check it yourself. The full URL is still a credential. On a channel that draws a preview card, send a test link first and see whether the preview counts a read, as in if you paste a one-time link into Slack or WeChat, does the preview burn it first. A Telegram cloud chat keeps plaintext too, and it syncs that plaintext to every device still on the list, so the full link stays out of a conversation whose sessions you have not finished cleaning.

Generate the new password itself with this site’s password generator. Random mode runs from 6 to 128 characters, the default is 16, and a length under 8 is flagged as weaker. The result is a password. You still press Change Password inside Discord yourself. The generated string is not uploaded as business data. This site’s strength check runs locally and compares against a top leaked-password list. That check cannot tell you whether a Discord token was read off this machine.

An export larger than 32 KB does not belong on a one-time text link. Use the file encryption box: streaming AES-256-GCM in the browser, one file up to 5 GB, output .lock or .enc, with the passphrase sent separately. Encrypt on this machine first, then send the file. Leaving an unencrypted session export, or a token pasted as text, inside a cloud chat is the same class of handoff as typing a login code into a window you do not recognize: whatever the other side can already read is the copy they can keep using.

Once you have seen another Discord window return to the login page, and you have ended the unrecognized row on Telegram’s device list, the title has a concrete answer. Changing the Discord password retires the token that could still sign in. Changing only the Telegram cloud password changes what the next login must present. The session file already sent can remain in the other chat until you end that row, and until then it can still sign in. Flare’s 24 September report put both jobs in one program. The cleanup is still two separate actions.

FAQ

I changed the Discord password. Is the token dead?

The help center says changing the password logs out every device, including logins you did not approve yourself. Another client that was already open returning to the login page is the result of that check. The other side’s chat log can still hold the old string. The string can remain in their history after it can no longer sign in. If SystemHelper.exe is still in the Startup folder, the next sign-in can still read a new token.

I changed the Telegram cloud password. Is that session gone too?

The session stays on the device list until you end it there. The FAQ writes “turn on two-step verification” and “end the session in the device list” as two steps. In the report, when a cloud password was already set, the code notes that the password was left unmodified and that what it took was a newly created session file. After you end the session, that file can remain on their side, and it should no longer be able to sign in. A device you just installed can refuse, for a while, to end an older session.

A window asked for my phone number and login code. How is that different from the official app?

The official client does not hand the login code to a script you opened from somewhere else, and it does not send a session file named after your phone number to someone else. The Telegram path in the report depends on you typing the phone number, the code, and, when two-step verification is on, the cloud password. Stop when you see that window. Leave the login code unforwarded. If you already typed it, work from the device list. A password change by itself leaves the new session listed.

Does this mean every password saved in Chrome was read?

That conclusion is outside this report. Flare says the Chrome path searches local storage in the default profile for strings shaped like a Discord token, and that it leaves the password store, cookies, and the browser’s encryption keys unread. Saved logins for other sites need their own check. “Local storage may hold a Discord token” covers that token. It leaves the rest of the password store as a separate question.

Do I need an account to create a one-time link? If I send the wrong channel, can support recover it?

No sign-up. Create and read are both public to a visitor. After the ciphertext burns by read count or by expiry, there is no server-side plaintext backup and no support inbox that can bring it back. Set a new password and create a new link. Leave the full s.html?id=…#… out of a Telegram cloud chat whose sessions you have not ended.