Channel
@BackupLSO
On this record: Growth · Engagement · Posts · Citations · Cite this entry
3,147subscribers
+16 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1002333840978 |
|---|---|
| Type | Channel |
| Username | @BackupLSO |
| Created | Between 1 September 2024 and 31 March 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 10 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 10 August 2026 |
| On Telegram | t.me/BackupLSO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 10 Aug 2026, 17:54 | 3,147 | +14 |
| 7 Aug 2026, 11:55 | 3,133 | +2 |
| 6 Aug 2026, 19:48 | 3,131 | first reading |
20 posts held, back to 14 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 4 pagesof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 7 August 2026 |
|---|---|
| Posts held | 20 (14 July 2026 – 7 August 2026) |
| Views total | 17,234 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 7 Aug 2026, 23:55 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
WAF Bypass Techniques + Tools Here are some powerful tools and methods to help you bypass Web Application Firewalls during bug hunting: 🔥 Tools: - wafw00f — WAF fingerprinting tool → https://github.com/EnableSecurity/wafw00f - bypass-firewalls-by-DNS-history — Discover origin IPs via old DNS records → https://github.com/vincentcox/bypass-firewalls-by-DNS-history - CloudFail — Excellent for bypassing Cloudflare …
⚠️HackLabs is a collection of hands-on vulnerable labs designed to practice web exploitation, privilege escalation, Active Directory attacks, and general pentesting techniques in a safe environment. ⚠️ For educational and authorized testing only. 🔗 https://github.com/afsh4ck/HackLabs ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
Roadmap for Cyber Security & Ai Security https://t.me/+390M0bSj10BiMDJk Membership is only for 100 people. ⭕ For 47
📌Bug Bounty Tip: Finding Confidential Documents Fast ✅Admins often leave these unredacted files online by mistake, making them a high-medium severity finding for bug bounty programs. ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
CloudRip Fast Cloudflare bypass scanner. A tool that helps you find the real IP addresses hiding behind Cloudflare by checking subdomains. https://github.com/moscovium-mc/CloudRip ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
Hi everyone, I’m currently developing an AI-powered chatbot on Telegram focused on the field of Cyber Security. If you’re interested in investing in this project or would like to learn more, feel free to reach out to me. Looking forward to connecting. @RedTeamKitBot
Claude-BugHunter — Turn Claude Code into a Senior Bug Hunter & Red Team Operator 🤖💀 A powerful skill bundle built for bug bounty hunters and external red teams. • 51 specialized security skills • 15 slash commands for automated workflows • 681 real disclosed report patterns • Coverage across Web, API, Cloud, OAuth, SAML, GraphQL, SSRF, IDOR, XSS, RCE & more • Enterprise attack paths for M365, Okta, VPNs, SharePoint…
😈Turn your Burp Suite findings into clean, professional cards, ready for reports, bug bounty submissions, and social sharing. 🚨https://github.com/JFOZ1010/repshot ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
2FA Bypass https://github.com/0xmaximus/Galaxy-Bugbounty-Checklist/tree/main/2FA%20bypass ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
⚠️403 bypass tools for bug bounty hunters: bypass-403 → https://github.com/iamj0ker/bypass-403 nomore403 → https://github.com/devploit/nomore403 4-ZERO-3 → https://github.com/Dheerajmadhukar/4-ZERO-3 byp4xx → https://github.com/lobuhi/byp4xx dontgo403 → https://github.com/mbrg/dontgo403 ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
🔥CVE-2026-41940 cPanel/WHM Authentication Bypass - Detection Artifact Generator 🚨https://github.com/watchtowrlabs/watchTowr-vs-cPanel-WHM-AuthBypass-to-RCE.py ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
Bug Bounty Reconnaissance-Phase 1 ❤ Share & Support Us 📰 @BackupLSO 📚 @LibrarySecOfficial
Showing the 12 most recent of 20 posts we hold for @BackupLSO. 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.
Citation-graph rank — 74,684 of 1,151,006entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
Named by 75 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. The 24 listed below are the most frequent namers; the rest are counted above but not each listed.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 10 August 2026 — this entry's latest reading, not the date you are reading this.
“Offensive LSO” (@BackupLSO), 3,147 subscribers as measured 10 August 2026. Telegram Register, tgregister.com/channel/BackupLSO.
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.