# Killergram: an Xposed module that strips sponsored messages from Telegram > Killergram is a GPL-3.0 Android Xposed module for Telegram that hides the sponsored messages shown between chats, and it also lets you copy or save messages in chats where the sender has enabled Restrict saving content. **shatyuka/Killergram** — Remove sponsored messages of Telegram - Repository: https://github.com/shatyuka/Killergram - Stars: 588 · Forks: 45 - Language: Java - License: GPL-3.0 - Published: 2026-10-22 · Updated: 2026-10-22 · Language: en - Canonical page: https://hysenlabs.com/projects/shatyuka-killergram ## A module for the message list, not a Telegram client Killergram is described as an Android Xposed module to remove sponsored messages of Telegram, which is a narrow, specific claim and worth holding on to. It is not a fork of Telegram and it is not a replacement client. It is a module, which is a different kind of artifact with a different set of constraints, and the support table at the top of the README is the clearest evidence of that. Instead of one application, the module lists 27 client names with their package identifiers: the official Android client under org.telegram.messenger, the web client under org.telegram.messenger.web and the beta under org.telegram.messenger.beta, the Plus Messenger build under org.telegram.plus, iMe Messenger, and a long list of forks including Forkgram in several variants, Nullgram, OctoGram, Cherrygram, exteraGram, TurboTel Pro, Catogram, Catogram X, Momogram, moeGramX, Mercurygram, OwlGram, Graph Messenger, aka, BGram, Nanogram and NekoX. The audience is a user on one of those clients who wants the interstitial posts gone. ## Package names are the contract, and two clients are partial Because the module attaches to a running application rather than replacing it, the package identifier is the contract between the module and the client. The README gives both the name and the package for every entry, which lets a user check their own client against the list before installing anything. Two entries carry a note, and the note is the same in both cases: Telegram X under org.thunderdog.challegram and moeGramX under moe.kirao.mgx are marked No Ads only. That is a meaningful detail rather than a formatting quirk, because it tells you that on those two clients the module performs the ad removal but not the other feature. A user who wants the message saving behaviour and happens to run one of those two clients should expect half the tool to be missing, and the README does not explain why, which is where the sparse documentation starts to matter. ## The second feature fights the Restrict saving content setting Beyond removing the sponsored messages, the module allows you to copy or save messages when Restrict saving content is enabled. That setting is a sender-controlled option in Telegram chats, and by default it stops the recipient from copying message text or forwarding it. The README is candid that this is a partial win: forwarding messages is still not working due to server limitation. So the module defeats the client side of the restriction, letting you take the text, while the server side of the check, which is what governs forwarding, still refuses. That is the honest shape of the feature and it is a useful one to understand before installing, because a user who wants to move a message between chats will find that copying works and forwarding does not. The module is a client side tool all the way through, and where the enforcement lives on the server it cannot reach. ## Release naming by date, and a repository that is mostly a build The release tags are named by date rather than by version number, with entries such as 26.08.24, 26.08.23 and 26.07.22, and the last push to the repository was on 2026-08-24. That convention makes it easy to tell at a glance which build you have, which matters for a module that has to keep pace with a client that ships new versions frequently. The repository layout is small and tells you what kind of project this is: an app/ directory holding the module itself, a build.gradle, settings.gradle, gradle.properties, the gradle/ wrapper directory, gradlew and gradlew.bat for the build, a LICENSE.md, the README, and a .gitignore. There is no test directory, no documentation directory, no issues templates and no contribution guide, and the README itself is the whole of the documentation. The primary language is Java. The licence is the GNU General Public Licence version 3, which is the same licence the Telegram clients themselves use, which is a natural pairing for a module that links against them. ## What the README does not tell you The documentation is thin, and anyone evaluating this should know exactly where the gaps are. There is no installation section, so the README does not say how you install the module, which frameworks it works with, or which Android versions it supports, and it does not point to a release page or a build guide. There is no section describing how the hooking is done, so the mechanism is invisible from the repository alone. There is no changelog beyond the tag names, no troubleshooting, and no explanation of the two No Ads only entries. The topics list is only telegram and xposed, and the project has no homepage recorded, so there is no site beyond the GitHub repository to consult. None of this means the tool does not work, but it does mean that the burden of working out whether it will work on your device and your client sits with you rather than with the project, and that is a real cost when a module has to be rebuilt for every new client release. ## Where Killergram is the wrong choice There are two clear cases. The first is a user on a platform the table does not cover. The list is a snapshot of clients as of a particular date, and the Telegram client ecosystem churns, with new forks appearing and old ones disappearing, so a client that is absent from the list is simply a client the module does not work with. The second is anyone who needs forwarding to work in restricted chats, which the README rules out on the grounds of a server limitation and no client side module can change. There is also a design question underneath both. A module that hides interface elements is tied to the internal view structures of each client, so a client update that renames a class or changes a layout can break it silently, and with 27 packages in scope that surface area is 27 times larger than it would be for a single client. The alternative worth naming is switching to a client that already omits the sponsored posts and has the features you want built in, since the forks listed in the table are numerous and some of them exist precisely to serve that preference. Killergram is the right answer when you like your current client and want exactly one thing changed. ## Conclusion Adopt Killergram if you run one of the listed Telegram clients on an Android device where a module framework is available, and the sponsored messages between your chats bother you. Do not adopt it expecting forwarding to work, because the README states that forwarding is still not working due to a server limitation. Verify first that your exact client and package name appear in the support table, since the module works per package and two of the listed clients are marked as ad removal only. ## FAQ ### What does the Killergram Xposed module actually do? It removes the sponsored messages that appear in Telegram, and it also allows you to copy or save messages when Restrict saving content is enabled. The README notes that forwarding messages is still not working due to a server limitation. ### Which Telegram clients does Killergram support? The README lists 27 clients with their package names, including the official Android, web and beta clients, Plus Messenger, iMe Messenger, NekoX, Nanogram, BGram, Catogram, Forkgram in several variants, aka, TurboTel Pro, Catogram X, OwlGram, Cherrygram, exteraGram, Telegram X, Graph Messenger, Nullgram, OctoGram, Mercurygram, Momogram and moeGramX. ### Does Killergram work the same way on every supported client? Not quite. Two entries in the support table carry a note, and for both of them the note reads No Ads only. Those are Telegram X under org.thunderdog.challegram and moeGramX under moe.kirao.mgx, so on those two clients the module removes the sponsored messages but not the other feature it offers. ### What licence is Killergram released under? The GNU General Public Licence version 3, the same licence the Telegram clients use. The repository carries a LICENSE.md alongside the README, and the implementation is Java in an app/ directory built with Gradle. ## Sources - [Issues](https://github.com/shatyuka/Killergram/issues) - [License: GPL-3.0](https://github.com/shatyuka/Killergram/blob/master/LICENSE) - [README](https://github.com/shatyuka/Killergram/blob/master/README.md) - [Releases](https://github.com/shatyuka/Killergram/releases) - [shatyuka/Killergram on GitHub](https://github.com/shatyuka/Killergram) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/shatyuka-killergram