Damus
Open in Damus
Final profile picture
Final
@Final
(updated post) The Nekogram telegram client contains code that grabs your Telegram ID and phone number to send to their own bots, also some other OSINT bots mentioned. They admitted to it in their channel (@NekoUpdates) and are insulting users in the comments. Assume your number and user can be correlated at a worst case. Keep away from third party clients.

https://github.com/Nekogram/Nekogram/issues/336

https://github.com/RomashkaTea/nekogram-proof-of-logging
2610❤️4👀3👍2🤔1🤦‍♂️1🪿1
Sancho Panza · 2d
Shit! Also better with official Telegram app?
Hello · 2d
What about Nagram?
chrizzz · 2d
I don't understand. Isn't Nekogram open source? Why all the adb and injection stuff? Is it not in the source?
NetSavior · 2d
The official telegram app now is asking me for an email and pay 0,80€ to send me a SMS 🤯🤷🏻‍♂
Ziggy · 2d
Unrelated - but any worries we should have about Molly client for Signal?
JesterHodl · 1d
Could AI help build a new wave of antivirus/antimalware software? Maybe I'm not in touch, but AI seems to disrupt everything but malware defense.
Lucia Ferreira · 1d
"Third-party Telegram clients have always carried risks—data scraping isn’t surprising, but Nekogram’s dismissive response is concerning. It’s a reminder that even ‘convenient’ alternatives can undermine opsec. Reminds me of how Telegram’s opacity fuels speculation elsewhere, like in I...
James Jesus Angleton Paranoia Culture - Paralysis creation excessive suspicion · 23h
"Third-party clients always carry risk—trade convenience for opacity. The Nekogram situation reminds me of a recent *The Board* piece on Telegram’s role in Iran’s protests, where metadata access had real-world consequences. Trust matters when tools can be weaponized. https://theboard.world/...