Telegram RegisterThe public register of Telegram
Telegram profile photo for 1st exploit

Channel

1st exploit

@firstpoc

On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry

131subscribers

+4 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002105520582
TypeChannel
Username@firstpoc
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live30 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 30 August 2026
On Telegramt.me/firstpoc

Growth

126131128.58 August 2026 — 127 subscribers9 August 2026 — 127 subscribers15 August 2026 — 126 subscribers24 August 2026 — 128 subscribers30 August 2026 — 131 subscribers8 August 202630 August 2026
5 measurements spanning 22 days, net +4. 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 125–132 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
30 Aug 2026, 10:48131+3
24 Aug 2026, 06:04128+2
15 Aug 2026, 18:58126-1
9 Aug 2026, 02:16127no change
8 Aug 2026, 06:47127first reading

Engagement

19 posts held, back to 17 September 2025the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
15.3%
avg views ÷ 131 subscribers
Avg views / post
20.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 19 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 8 August 2026
Posts held19 (17 September 20258 August 2026)
Views total20
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 02:16 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

16 reactions across 8 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 5289722755871162900850.0%
custom 5307882075167145025531.3%
custom 5449875850046481967318.8%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

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 8 of the 19 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 16reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 17 September 2025 to 8 August 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

8 Aug 2026, 17:35 UTC20 viewsread 9 August 2026
File

* First PoC for CVE-2026-64638 > Boreas37/CVE-2026-64638-PoC CVE: CVE-2026-64638 | Created: 2026-08-07 Desc: XSS2Shell (CVE-2026-64638) PoC — WordPress pre-auth XSS to RCE chain Link: Boreas37/CVE-2026-64638-PoC Files (3): - .gitignore - README.md - xss2shell.py

21 Jul 2026, 05:01 UTC76 viewsread 9 August 2026
File

* First PoC for CVE-2026-31278 > mda1r/CVE-2026-31278 CVE: CVE-2026-31278 | Created: 2026-03-25 Desc: CVE write-up for Active Directory credential exposure vulnerability in Suprema BioStar 2 Link: mda1r/CVE-2026-31278 Files (1): - README.md

21 Jul 2026, 05:00 UTC75 viewsread 9 August 2026
File

* First PoC for CVE-2026-62183 > NicPWNs/CVE-2026-62183 CVE: CVE-2026-62183 | Created: 2026-07-20 Desc: Apache Syncope: User self-service privilege escalation Link: NicPWNs/CVE-2026-62183 Files (4): - .gitattributes - BUILD.md - README.md - poc.sh

21 Jul 2026, 05:00 UTC70 viewsread 9 August 2026
File

* First PoC for CVE-2026-12191 > hakaioffsec/CVE-2026-12191 CVE: CVE-2026-12191 | Created: 2026-07-20 Desc: PoC for CVE-2026-12191 Link: hakaioffsec/CVE-2026-12191 Files (4): - README.md - exploit.py - generate_payloads.py - simulate_victim.py

20 Jul 2026, 19:56 UTC65 viewsread 9 August 2026
File

* First PoC for CVE-2026-44680 > CerberusMrXi/CVE-2026-44680-MikroORM-SQL-Injection-Exploit-Framework CVE: CVE-2026-44680 | Created: 2026-07-20 Desc: PoC tool for CVE-2026-44680 affecting MikroORM ≤7.0.13. Exploits JSON path injection to extract database contents via UNION-based attacks. Features vulnerability detection, automated data extraction, table enumeration, and blind injection support. Includes proxy integ

20 Jul 2026, 19:55 UTC57 viewsread 9 August 2026
File

* First PoC for CVE-2026-16219 > HELLBOY3110/cve-2026-16219-croogo-lab CVE: CVE-2026-16219 | Created: 2026-07-20 Link: HELLBOY3110/cve-2026-16219-croogo-lab Files (26): - CHANGELOG.md - CONTRIBUTING.md - DISCLAIMER.md - GITHUB_UPLOAD.md - LICENSE - MANIFEST.md - Makefile - README.md - SECURITY.md - VERSION - demo/README.md - demo/path_authorization_demo.php - docs/detection.md - docs/lab-setup.md - docs/references

20 Jul 2026, 19:55 UTC57 viewsread 9 August 2026
File

* First PoC for CVE-2026-11374 > BishopFox/CVE-2026-11374-check CVE: CVE-2026-11374 | Created: 2026-07-20 Desc: Detection script for CVE-2026-11374 Link: BishopFox/CVE-2026-11374-check Files (6): - .github/CODEOWNERS - CONTRIBUTING.md - LICENSE - README.md - SECURITY.md - cve_2026_11374_check.py

20 Jul 2026, 15:53 UTC61 viewsread 9 August 2026
File

* First PoC for CVE-2026-60121 > HORKimhab/CVE-2026-60121-CVE-2026-61498 CVE: CVE-2026-60121 | Created: 2026-07-20 Desc: CVE-2026-60121, CVE-2026-61498 - Draft Link: HORKimhab/CVE-2026-60121-CVE-2026-61498 Files (5): - .gitignore - CVE-2026-60121.pdf - CVE-2026-61498.pdf - LICENSE - README.md

20 Jan 2026, 10:49 UTC316 viewsread 9 August 2026
File

CVE-2025-7441 — StoryChief ≤ 1.0.42 (WordPress) Unauthenticated arbitrary file upload throught endpoint /wp-json/storychief/webhook. The plugin downloads and saves a file from a URL specified in the JSON payload (data.featured_image.data.sizes.full), without verifying the domain, file type, or content. The file is stored in the wp-content/uploads/ directory. If executable file extensions are used (e.g., .php) and P

8 Nov 2025, 04:51 UTC383 views1 reactionsread 9 August 2026
Photo

Proof-of-Concept CVE-2025-9491: using invisible characters in the arguments of a Windows shortcut file .lnk (07 nov 2025) WriteUp

custom 52897227558711629001

3 Nov 2025, 12:56 UTC322 views2 reactionsread 9 August 2026
Photo

Bypassing WiFi Client Isolation (14 Oct 2025) PoC WriteUp

custom 52897227558711629002

3 Nov 2025, 11:29 UTC265 views2 reactionsread 9 August 2026
Photo

CVE-2025-62725: From “docker compose ps” to System Compromise (28 Oct 2025) PoC WriteUp

custom 53078820751671450252

Showing the 12 most recent of 19 posts we hold for @firstpoc. 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.

Mentions

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.

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 30 August 2026 — this entry's latest reading, not the date you are reading this.

“1st exploit” (@firstpoc), 131 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/firstpoc.

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.