HIGH DA/PA AND EDU GOV WEBSHELL AVAILABLE 📌 Posting this as an advertisement for SELLER I’m not the seller and don’t provide any guarantee for the service. For details, contact SELLER(@altafhossainff) directly.

Channel
CaptainSmok3r
@captainsmok3r_official
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
347subscribers
+44 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1002660409812 |
|---|---|
| Type | Channel |
| Username | @captainsmok3r_official |
| Created | Between 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 September 2026 |
| Last confirmed live | 12 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 12 September 2026 |
| On Telegram | t.me/captainsmok3r_official |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Sept 2026, 10:18 | 347 | +6 |
| 8 Sept 2026, 00:22 | 341 | no change |
| 5 Sept 2026, 03:59 | 341 | +2 |
| 29 Aug 2026, 04:58 | 339 | +7 |
| 22 Aug 2026, 15:11 | 332 | +18 |
| 14 Aug 2026, 22:33 | 314 | +9 |
| 8 Aug 2026, 03:23 | 305 | +2 |
| 7 Aug 2026, 18:24 | 303 | first reading |
Engagement
20 posts held, back to 29 August 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 1 page of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 24.9%
- avg views ÷ 347 subscribers
- Avg views / post
- 86.3
- 20 posts measured
- Reaction rate
- 1.82%
- reactions ÷ views · ER floor
- Posts in window
- 20
- of 20 held
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. It is computed over the 1 of 20 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 6 September 2026 |
|---|---|
| Posts held | 20 (29 August 2026 – 6 September 2026) |
| Views total | 1,727 |
| Reactions total | 2 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Sept 2026, 00:22 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.
Reaction mix
2 reactions across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 2 | 100.0% |
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 1 of the 20 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 2 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 29 August 2026 to 6 September 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.
Recent posts
CVE-2026-86189 (CVSS 9.8) — WWBN AVideo Path Traversal CVE-2026-86184 (CVSS 9.8) — Lara Dashboard Authentication Bypass. CVE-2026-83627 (CVSS 9.8) CVE-2026-10196 (CVSS 9.8) CVE-2026-13447 (CVSS 9.8)
CVE-2026-6471 (PostGREShell) a high-severity security vulnerability in PostgreSQL logical decoding that allows a user with replication privileges to run arbitrary code and gain full superuser control over the database server. poc: https://github.com/0xBlackash/CVE-2026-6471
CVE-2026-11613 poc: https://github.com/Wayang1337/CVE-2026-11613
CVE-2026-40976 is a critical security vulnerability in Spring Boot 4.0.0 through 4.0.5 that allows unauthenticated attackers to bypass authorization and gain unauthorized access to all application endpoints poc: https://github.com/madebyrokit/CVE-2026-40976-POC/blob/main/poc.py
CVE-2026-14494 The Sigma Forms Pro plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1.4.5 via the handle_form_submission function. This is due to the plugin dynamically granting the unfiltered_upload capability to all users during form submissions and bypassing MIME type validation when allowed_file_types is not configured. This makes it possible for unauthenticated at…
👀 CVE-2026-19949 👀
python poc.py -u http://35.227.205.53/ --token ╔══════════════════════════════════════════════════════════╗ ║ artifactory · CVE-2026-82329 unauth admin takeover ║ ║ mitsec · https://x.com/ynsmroztas ║ ╚══════════════════════════════════════════════════════════╝ [*] targets=1 threads=8 [VULN] http://35.227.205.53 join=201 svc_scp=admin admin token scp=applied-permissions/admin aud=* conf…
CVE-2026-82329-JFrog-Artifactory-Auth-Bypass poc published in github: https://github.com/ynsmroztas/CVE-2026-82329-JFrog-Artifactory-Auth-Bypass
CVE-2026-18431 Avada Theme + Fusion Builder – Unauthenticated RCE via Arbitrary File Write
CVE-2026-78292 Unauthenticated PHP Object Injection in Hash Form <= 1.4.1 versions.
CVE-2026-15369- Custom User Registration Fields for WooCommerce <= 2.2.3 - Unauthenticated Privilege Escalation via 'afreg_select_user_role' Parameter in Store API Checkout
Showing the 12 most recent of 20 posts we hold for @captainsmok3r_official. 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.
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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 12 September 2026 — this entry's latest reading, not the date you are reading this.
“CaptainSmok3r” (@captainsmok3r_official), 347 subscribers as measured 12 September 2026. Telegram Register, tgregister.com/channel/captainsmok3r_official.
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.