Telegram RegisterThe public register of Telegram
Telegram profile photo for LSPosed

Channel

LSPosed

@LSPosed

On this record: Topic · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Telegram's recommendations · Cross-platform identity · Referenced elsewhere · Cite this entry

202,699subscribers

+15,970 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 100,000–316,228.

Register entry

Telegram ID-1001499638348
TypeChannel
Username@LSPosed
DescriptionOfficial webpage: lsposed.org Discussion Group: @LSPosedDiscussion CI Builds: @LSPosedArchives Admin Log: @lsposed_log
CreatedBetween 1 April 2020 and 31 December 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 November 2026
Measurements held67
Confirmed unchanged1 time, most recently 19 November 2026
On Telegramt.me/LSPosed

Topic

Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-UD-Q6_K_XL, prompt version 1) read this channel’s own recent posts on 8 August 2026 and assigned it the closest of 31 fixed categories, at 87% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

186,729202,699194,7146 August 202619 November 2026
67 measurements spanning 104 days, net +15,970. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 184,334–205,095 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 67
Measured (UTC)SubscribersChange
19 Nov 2026, 02:55202,699+515
16 Nov 2026, 01:27202,184+560
12 Nov 2026, 11:55201,624+310
10 Nov 2026, 07:01201,314+181
8 Nov 2026, 17:14201,133+280
7 Nov 2026, 09:10200,853+188
6 Nov 2026, 05:40200,665+120
5 Nov 2026, 04:36200,545+141
4 Nov 2026, 02:21200,404+126
3 Nov 2026, 01:19200,278+78
2 Nov 2026, 03:10200,200+140
1 Nov 2026, 02:56200,060+167
31 Oct 2026, 05:40199,893+137
30 Oct 2026, 09:06199,756+85
29 Oct 2026, 10:16199,671+132
28 Oct 2026, 07:40199,539+125
27 Oct 2026, 09:39199,414+160
26 Oct 2026, 11:39199,254+105
25 Oct 2026, 14:49199,149+233
24 Oct 2026, 13:36198,916first reading

Engagement

29 posts held, back to 4 September 2025 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 214 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 29 posts for this entry, the most recent from 15 October 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
27
Videos
3
Links
59

Lifetime counters from Telegram’s own channel header, read 20 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Video runtime
4m 09s
Average length
2m 05s

Measured directly from 2 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.

Reaction mix

23,363 reactions across 29 posts, in 33 distinct kinds. The most used accounts for 45.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍10,50645.0%
❤8,44336.1%
😭9404.02%
🔥7063.02%
🍾4421.89%
🥰3991.71%
🎉3301.41%
❤‍🔥2841.22%
🤩2330.997%
👏2030.869%
💯1790.766%
🏆1730.74%
🤗1140.488%
😱780.334%
😍760.325%
🤣340.146%
😡330.141%
👎280.12%
😢270.116%
💅250.107%
13 further kinds1100.471%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 29 of the 29 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 23,363 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 29 most recent posts we hold, published 4 September 2025 to 15 October 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
668
across the posts below
Posts paid on
24
of 29 we hold a reading for · 83%
Most on one post
111
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @LSPosed. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 29 most recent posts we hold for this entry, published 4 September 2025 to 15 October 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

15 Oct 2026, 02:47 UTC≈97,100 views759 reactionsread 20 November 2026
File

This announcement formally introduces DexSQL, accessible via the following link: https://github.com/LSPosed/dexsql-release. The project facilitates the analysis of APK dex files using SQL, specifically for deobfuscation and the identification of hook points. Compared to tools such as JADX and similar counterparts like ASC, DexSQL offers significantly superior performance and memory consumption, as illustrated in the …

👍498❤163🥰37🔥19🎉15🤡9💅5🤔5

13 Oct 2026, 15:13 UTC≈98,300 views415 reactionsread 20 November 2026

https://x.com/realnullptr/status/2110025105338519970?s=20

👍288❤41😢27😭23🤣8🫡6💅5🤝5

5 Oct 2026, 02:39 UTC≈243,000 views1,137 reactionsread 20 November 2026

LSPosed v2.2.1 从本次更新开始,安装包使用 XZ 压缩以减小体积,2024 年 8 月后的所有 root 实现均已支持 XZ 压缩方式。 Starting with this update, installation packages use XZ compression to reduce their size. All root implementations released after August 2024 support XZ compression. 新增 - 恢复提供 riscv64 ABI 支持 - 支持 Android 17 QPR 3 - 提升 KernelSU 最低管理器版本要求到 1.0.1 - 新增开发者模式与命令行工具 lspctl,支持管理模块及作用域等功能 - 新增禁用安全模式的选项 - 新增横移返回手势开关 改进 - 大幅优化调用链性能,钩子执行成本约 27x speedup …

👍792❤156🔥62😡33👎25🌚14💯14🌭12

14 Sept 2026, 11:38 UTC≈194,000 views1,285 reactionsread 20 November 2026

The libxposed organization has been flagged by GitHub, to access the source code or java doc, you can download the relevant files from the Maven Central Repository. libxposed 组织已被 GitHub 封锁,如需查阅源代码或文档,可在 maven 中央仓库下载相关文件。 https://repo.maven.apache.org/maven2/io/github/libxposed

😭916👍114😱78❤72🤣26🍾23🤨23🔥14

10 Sept 2026, 13:07 UTC≈196,000 views363 reactions6 Starsread 20 November 2026

libxposed future proposal: DexSQL DexSQL lets you query Android DEX files with SQL, it replaces the DexParser that was deprecated in libxposed API 100. It is now available for early access—feedback on slow or failing SQL statements is welcome. libxposed 新功能提案:DexSQL DexSQL 允许使用 SQL 语句查询 Android DEX 文件结构,它取代了libxposed API 100 中被废弃的DexParser。 现在可以抢先试用,欢迎反馈缓慢或者失败的SQL语句。 https://dexsql.lsposed.org/

👍232❤75🔥36🍾8🥰7🤗4😭1

9 Sept 2026, 01:14 UTC≈188,000 views356 reactions1 Starread 20 November 2026

https://github.com/LSPosed/LSPromise

👍243🔥43❤42🥰14👏8💯4❤‍🔥2

3 Sept 2026, 05:19 UTC≈168,000 views722 reactions6 Starsread 20 November 2026

Due to the increasing prevalence of AI and the accelerated submission of new modules, we plan to upgrade our module repository to an automated approval mode. Following the approach of the Maven Central Repository, submitters will need to prove they control the domain name to which the module package name belongs. If there is no domain name, you can use io.github.[user name].[module name], which will automatically app…

👍539❤122😍20🔥11🤗7🥰6🍾5🎉5

31 Aug 2026, 14:39 UTC≈147,000 views401 reactionsread 20 November 2026
File

另外系统自带 docker,在 /data/docker/docker

👍315❤35❤‍🔥13🍾13🤗10🤩4🥰4👏3

30 Aug 2026, 04:07 UTC≈254,000 views677 reactions3 Starsread 20 November 2026

v2.2.0 重要 - New XSharedPreferences 计划于 2.3.0 正式移除,模块页面已为有兼容风险的模块加入废弃警告。判断逻辑为 legacy 模块声明支持 nsp 并存在 others 可读 xml。升级到 libxposed 或将 xposedminversion 设置为 82 并删除 xposedsharedprefs 以移除警告。 新增 - 支持注入 HyperOS Runtime 应用(需要兼容 Zygisk Next API 的 Zygisk 实现) - 在 A17 及以上以注入方式处理 dex2oat 包装器,避免挂载泄漏(需要兼容 Zygisk Next API 的 Zygisk 实现) 改进 - 提升多进程应用中模块服务连接的稳定性 - 优化管理器中的兼容性状态展示与异常提示 修复 - 修复资源 Hook XML 重写长期失效的问题 - 修复模块热重载失败后可能产生状态异常的问题 …

👍460❤121🤩25🔥24🥰17❤‍🔥12🍾7👏6

4 Aug 2026, 16:29 UTC≈242,000 views1,435 reactions5 Starsread 20 November 2026

我们在 Android 17.0 中发现了一个特权进程任意代码执行漏洞。该漏洞已在 Android 17 QPR1 中修复,但 AOSP 安全公告中并未提及。结合 dirty frag 漏洞(CVE-2026-43284),我们在 Android 17.0 上成功实现了完整的 root 权限提升。 这是一个典型的 1day 漏洞。尽管补丁已发布,但用户无法获得漏洞修复,因此仍面临被攻击的风险:任何人都可以通过对比分析发现该漏洞的细节。而 dirty frag 漏洞虽已于三个月前披露,但至今仍可被利用。这是因为谷歌推迟了漏洞补丁的发布频率,将安全公告从每月一次改为每季度一次。在 AI 时代,这种做法不可理喻。由于 Pixel 系统镜像中泄露的漏洞细节,Android 生态中的大量设备都容易受到攻击,未参与 Beta 测试计划的 Pixel 设备也无法幸免。 因此,我们利用两个“已经”修复过的漏洞,演示了对安装有最新安全补丁的 …

👍1,050❤227🤩57❤‍🔥27🍾18🔥15🤗13💯11

4 Aug 2026, 16:28 UTC≈206,000 views568 reactions3 Starsread 20 November 2026
Video

We discovered a privileged process arbitrary code execution vulnerability in Android 17. This vulnerability was patched in Android 17 QPR1 but was not included in any security bulletin. Combined with the dirty frag vulnerability (CVE-2026-43284), we achieved full root privilege escalation on Android 17.0. The DirtyFrag vulnerability was disclosed 3 months ago but is still exploitabe, because Google has delayed the r…

👍338❤143🔥37👏16❤‍🔥7💯7🍾5🥰5

23 Jul 2026, 16:20 UTC≈354,000 views1,075 reactions4 Starsread 20 November 2026

v2.1.1 新增 - 最低支持版本提升至 Android 9(API 28) - 高级隐藏功能现可支持 A12+ - 允许一键清空已选作用域 改进 - 优化安全模式对 System UI 的检测阈值 - 恢复管理器中的模块数量徽标 - 改进错误报告发送流程 修复 - 修复部分情况下无法启动守护进程的问题 - 修复 XposedHelpers.findField API 行为 - 修复 Android 17 下服务连接接口不兼容的问题 - 修复模块详情页弹出菜单显示层级异常的问题 - 修复 Markdown 样式在部分页面中显示异常的问题 Added - Raised the minimum supported version to Android 9 (API 28) - Advanced hiding is now supported on Android 12 and above - Added an option …

❤772👍151❤‍🔥35🤩23🍾17🔥17🥰17🏆16

Showing the 12 most recent of 29 posts we hold for @LSPosed. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 16 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Channels Telegram recommends alongside this one

Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.

5ec1cff
@real5ec1cff · 40,431
#1
Real Nullptr
@nullptr_dev · 21,547
#2
HyperCeiler | Canary Test
@cemiuiler_canary · 21,741
#3
Magisk alpha
@magiskalpha · 66,563
#4
AdClose Official
@AdClose · 12,491
#5
Android Software Hub
@ksc666 · 15,047
#6
akashaProxy ci channel
@akashaProxy · 1,832
#7
Reveny
@reveny1 · 7,558
#8
Voyager HyperOS Update
@VoyagerMIUIUpdate · 22,395
#9
不靠谱的喵(>^ω^<) #CatGPT
@MlgmXyysd_bibilailai · 22,561
#10
在花🎗️科技圈
@zaihuapd · 291,048
#11
橘橘橘子汁 & 🍊
@microblock_pub · 16,122
#12
风向旗参考快讯
@xhqcankao · 175,261
#13
RandomFree
@c001apk · 6,463
#14
我喜欢你
@bakaPD · 10,926
#15
Sakion Team
@Sakion_Team · 2,066
#16
Magisk Base || Magisk modules and other
@magiskmodules22 · 12,954
#17
InstallerX
@InstallerX · 9,036
#18
NPatch
@NPatch · 20,122
#19
企业级欢乐花园
@MaterialDesign3 · 9,211
#20
LibChecker CI
@libchecker_ci · 3,638
#21
QAuxiliary CI Builds
@QAuxiliary_CI · 19,703
#22
蓝点网订阅频道
@landiansub · 47,574
#23
QQ/TIM Update Log
@qq_updatelog · 6,993
#24
LoopDNS资讯播报
@DNSPODT · 73,443
#25
QQ Updates
@QQUpdates · 10,283
#26
HyperCeiler | Release & Notice
@cemiuiler_release · 28,202
#27
XiReiki
@xiayinlily · 2,871
#28
Pillboard
@Pillboard · 3,477
#29
Pzqqt's News Channel
@pzqqt_c · 4,008
#30
VPS信号旗播报
@vps_xhq · 51,119
#31
每日消费电子观察
@CE_Observe · 78,049
#32
Project X Channel
@projectXtls · 30,665
#33
柒柒的鱼骨头
@Sandrone0721 · 1,131
#34
Bilibili Android Apk w/ HD
@bilibili_apk · 4,149
#35
Hakuma is cute ~
@huskydg · 4,092
#36
秋风のとおり道
@AWAvenue · 26,101
#37
Wa Enhancer Updates & Tips
@waenhancher · 37,002
#38
Pixel Props
@PixelProps · 14,440
#39
GApps Leaks
@GappsLeaks · 21,705
#40
WSTprojects
@WSTprojects · 28,053
#41
Play integrity fix NEXT
@PifNEXT · 6,849
#42
DrDisagree's Projects
@DrDsProjects · 9,941
#43
Loop Projects | #TeamFiles
@loopprojects · 9,697
#44
Mishaal's Android News Feed
@MishaalAndroidNews · 11,672
#45
Android dumps
@android_dumps · 5,758
#46
[DISCONTINUED] Rboard Themes
@rkbdigboard · 5,834
#47
PUI The Newsroom 😍
@PUINewsroom · 14,236
#48
Nagram
@nagram_channel · 75,211
#49
XPL-EX
@xpl_ex · 3,062
#50
Nullgram
@NullgramClient · 9,065
#51
SafetyNet, CTS, and Play integrity
@ctsfixes · 2,423
#52
APC - Android Ports Cloud
@apcports2 · 8,929
#53
不要糖醋放椒盐
@saltplayerupdate · 17,653
#54
MrSluffy's Prjkt
@mrsluffy_releases · 5,942
#55
SnapEnhance
@snapenhance · 9,482
#56
RKBDI rant channel
@RKBDIchannel · 1,878
#57

Read from Telegram’s recommendation API, most recently 17 August 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

Hide My Applist
@HideMyApplist · 42,210
Telegram ranks this channel #1 of 24 here — alongside 23 others — read 30 August 2026
Magisk alpha
@magiskalpha · 66,563
Telegram ranks this channel #1 of 40 here — alongside 39 others — read 21 August 2026
Real Nullptr
@nullptr_dev · 21,547
Telegram ranks this channel #2 of 54 here — alongside 53 others — read 28 September 2026
LSPosedArchives
@LSPosedArchives · 27,631
Telegram ranks this channel #2 of 36 here — alongside 35 others — read 14 September 2026
5ec1cff
@real5ec1cff · 40,431
Telegram ranks this channel #2 of 51 here — alongside 50 others — read 2 September 2026
QAuxiliary
@QAuxiliary · 44,409
Telegram ranks this channel #3 of 58 here — alongside 57 others — read 12 September 2026
HyperCeiler | Canary Test
@cemiuiler_canary · 21,741
Telegram ranks this channel #5 of 49 here — alongside 48 others — read 4 October 2026
Surfboard News
@surfboardnews · 28,377
Telegram ranks this channel #5 of 64 here — alongside 63 others — read 9 September 2026
哔哩漫游
@biliroaming · 56,347
Telegram ranks this channel #6 of 50 here — alongside 49 others — read 12 September 2026
KernelSU
@KernelSU · 76,504
Telegram ranks this channel #8 of 49 here — alongside 48 others — read 14 September 2026
SCENE Downloads
@scene2023 · 57,928
Telegram ranks this channel #12 of 50 here — alongside 49 others — read 12 September 2026
Github_2dust
@github_2dust · 93,166
Telegram ranks this channel #13 of 71 here — alongside 70 others — read 17 August 2026
LuckyTool
@LuckyTool · 31,772
Telegram ranks this channel #15 of 56 here — alongside 55 others — read 12 September 2026
Nagram Tips
@NagramTips · 53,197
Telegram ranks this channel #17 of 49 here — alongside 48 others — read 30 August 2026
APatch Updates
@APatchChannel · 26,083
Telegram ranks this channel #18 of 37 here — alongside 36 others — read 14 September 2026
BSG MGC Public Release Channel
@Channel_MGC_BSG · 42,669
Telegram ranks this channel #23 of 58 here — alongside 57 others — read 7 September 2026
FlClash Channel
@FlClash · 55,585
Telegram ranks this channel #23 of 53 here — alongside 52 others — read 28 August 2026
Clash Verge Rev Channel
@clash_verge_re · 86,759
Telegram ranks this channel #23 of 64 here — alongside 63 others — read 19 August 2026
NPatch
@NPatch · 20,122
Telegram ranks this channel #25 of 48 here — alongside 47 others — read 2 October 2026
QAuxiliary CI Builds
@QAuxiliary_CI · 19,703
Telegram ranks this channel #26 of 56 here — alongside 55 others — read 1 October 2026
HyperCeiler | Release & Notice
@cemiuiler_release · 28,202
Telegram ranks this channel #26 of 51 here — alongside 50 others — read 12 September 2026
Legado|开源阅读|频道
@Legado_Channels · 93,081
Telegram ranks this channel #30 of 61 here — alongside 60 others — read 17 August 2026
Matsuridayo GitHub
@MatsuriDayo · 45,766
Telegram ranks this channel #31 of 58 here — alongside 57 others — read 30 August 2026
FunProject
@QToolCI · 50,652
Telegram ranks this channel #33 of 51 here — alongside 50 others — read 12 September 2026

This channel appears in 34 seed channels' Telegram-generated recommendation lists in total, of which the 24 where it ranks highest are shown above. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

Cross-platform identity — Wikidata

A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.

Q114903881 on Wikidata, read 15 November 2026
LabelLSPosed
DescriptionAndroid module framework based on EdXposed
Official sitehttps://lsposed.org/

Referenced elsewhere

This handle named by sources this register does not control and did not measure — each shown exactly as found, attributed by name, dated to when it was read.

Wikipedia

One Wikipedia article names this handle in its article text, found by searching for a t.me link inside the article source. A citation is a notability signal, not a verification: nobody here confirmed the cited post is genuine or still says what the article quotes. Article text is CC BY-SA 4.0, Wikipedia contributors; snippets below are short excerpts.

Xposed Framework (en.wikipedia.org)
“…com/lsposed/ |url-status=live}}{{Cite web |title=LSPosed |url=https://t.me/LSPosed/324 |access-date=2026-09-11 |website=Telegram}} === Vector…”
read 1 November 2026

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 19 November 2026 — this entry's latest reading, not the date you are reading this.

“LSPosed” (@LSPosed), 202,699 subscribers as measured 19 November 2026. Telegram Register, tgregister.com/channel/LSPosed.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.