Forwarded from Tech & Leaks Zone
EXPOSED: Source Code Evidence of Nekogram Phone Number Harvesting
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone
1. Exfiltration Logic: The function uo5.g() (reconstructed as logNumberPhones) silently collects the UserID and Phone Number of every account logged into the app (up to 8 accounts).
2. Transmission: Data is sent via Inline Queries to the bot @nekonotificationbot. This is done programmatically, so no message appears in your "Sent" history.
3. Target Bots: Three bots embedded in the client's obfuscated code:
@nekonotificationbot: Receives the automated phone number uploads.
@tgdb_search_bot and @usinfobot: : An OSINT bot mentioned in the obfuscated classes.
4. Security Token: The app uses a hardcoded secret key 741ad28818eab17668bc2c70bd419fc25ff56481758a4ac87e7ca164fb6ae1b1 as a prefix for the stolen data, likely to authenticate with the bot's backend.
5. The image shows that Nekogram always wants to get the "reg date".
Unfortunately the Google Play Store version is also affected!!!
Follow @TechLeaksZone
Tech & Leaks Zone
Photo
I'm starting to believe that every third party telegram client is having something like this not gonna lie.
Where to go? Probably Forkgram.
That telegram Client is the ONLY one that PASSED F-Droid.
And F-Droid are strict with their apps list.
Where to go? Probably Forkgram.
That telegram Client is the ONLY one that PASSED F-Droid.
And F-Droid are strict with their apps list.
T.R.M.'s Flexes (Channel)
Also, are you guys moving to Artix?
I kinda wished Artix works like CachyOS, where they put their packages on top of arch instead of recompiling everything on their own
Also, their region specific mirrors is less than arch did, and at the same time not synced properly with their main repos
Also, their region specific mirrors is less than arch did, and at the same time not synced properly with their main repos
https://www.instagram.com/reel/DWoyH-qDoS8/
imagine u r struggling because microslop broke your outlook
imagine u r struggling because microslop broke your outlook
T.R.M.'s Flexes (Channel)
T.R.M.'s Xiaomi Edits - Perf Neon Weekly "The Journey of Umamusume Dreams" > Information > Releases TL;DR > Built on: 2026/03/29, Unix Timestamp 1774762374 > ReSukiSU version name: v4.1.0-575ea1a1@ReSukiSU > ReSukiSU version code: 34681 > ReSukiSU KPM: falseβ¦
SUSFS builds are currently suspended because of JackA1ltMan SUSFS Inline Hooks is failing to patch hooks needed for ReSukiSU.
This media is not supported in your browser
VIEW IN TELEGRAM
T.R.M.'s Flexes (Channel)
Lol yea, but it deteched from the main group
So you're gonna kill this?
More like i'm not gonna use it anymore
Maybe same thing as killed
Maybe same thing as killed