Telegram RegisterThe public register of Telegram
Telegram profile photo for 1N73LL1G3NC3

Channel

1N73LL1G3NC3

@P0x3k_1N73LL1G3NC3

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · What this channel posts · Reactions · Stars · Advertising · Posts · Posts edited after publishing · Citations · Cite this entry

8,285subscribers

+878 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1002403863758
TypeChannel
Username@P0x3k_1N73LL1G3NC3
DescriptionDonate BTC: bc1qslpr2rpffa4cqprhw6hzzjqdufmsc2svw87f4a
CreatedBetween 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live17 November 2026
Measurements held29
Confirmed unchanged1 time, most recently 17 November 2026
On Telegramt.me/P0x3k_1N73LL1G3NC3

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 11 August 2026 and assigned it the closest of 31 fixed categories, at 99% 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.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (6 of the pairs behind the counts below)
Posted firstThenOverlapGap
@P0x3k_1N73LL1G3NC3/454 · this entry29 Oct 2026, 10:10 UTC@IRCyberGuardians/41232 Nov 2026, 14:30 UTC0.994 days
@P0x3k_1N73LL1G3NC3/462 · this entry4 Nov 2026, 16:06 UTC@IRCyberGuardians/41337 Nov 2026, 15:32 UTC0.993 days
@P0x3k_1N73LL1G3NC3/391 · this entry15 Jul 2026, 15:26 UTC@IRCyberGuardians/39273 Aug 2026, 14:30 UTC0.9919 days
@P0x3k_1N73LL1G3NC3/419 · this entry19 Aug 2026, 17:40 UTC@IRCyberGuardians/395829 Aug 2026, 14:30 UTC0.9910 days
@P0x3k_1N73LL1G3NC3/421 · this entry21 Aug 2026, 08:41 UTC@IRCyberGuardians/396029 Aug 2026, 14:30 UTC0.998 days
@P0x3k_1N73LL1G3NC3/408 · this entry11 Aug 2026, 19:14 UTC@IRCyberGuardians/395112 Aug 2026, 17:47 UTC0.9823 hours
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@IRCyberGuardians12 (8/8 hand-verifiable sample passed)0.996 daysthis entry (12–0)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 0 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 53 comparable posts for this entry, running 26 June 2026 to 16 November 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @APT_Notes. That channel is not among the channels listed above, so this entry may share no posts with it and this does not say where this entry’s content came from. It is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_source, last confirmed 17 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. 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

7,4078,2857,8466 August 2026 — 7,407 subscribers6 August 2026 — 7,407 subscribers7 August 2026 — 7,409 subscribers10 August 2026 — 7,485 subscribers13 August 2026 — 7,547 subscribers16 August 2026 — 7,601 subscribers19 August 2026 — 7,618 subscribers22 August 2026 — 7,652 subscribers25 August 2026 — 7,668 subscribers28 August 2026 — 7,684 subscribers31 August 2026 — 7,723 subscribers4 September 2026 — 7,756 subscribers9 September 2026 — 7,792 subscribers13 September 2026 — 7,803 subscribers17 September 2026 — 7,823 subscribers25 September 2026 — 7,894 subscribers5 October 2026 — 7,925 subscribers11 October 2026 — 7,959 subscribers14 October 2026 — 7,973 subscribers17 October 2026 — 7,979 subscribers20 October 2026 — 7,989 subscribers23 October 2026 — 8,063 subscribers26 October 2026 — 8,098 subscribers30 October 2026 — 8,150 subscribers2 November 2026 — 8,198 subscribers5 November 2026 — 8,209 subscribers8 November 2026 — 8,227 subscribers12 November 2026 — 8,244 subscribers17 November 2026 — 8,285 subscribers6 August 202617 November 2026
29 measurements spanning 103 days, net +878. 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 7,275–8,417 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 29
Measured (UTC)SubscribersChange
17 Nov 2026, 16:488,285+41
12 Nov 2026, 11:198,244+17
8 Nov 2026, 04:178,227+18
5 Nov 2026, 03:068,209+11
2 Nov 2026, 13:398,198+48
30 Oct 2026, 03:198,150+52
26 Oct 2026, 19:208,098+35
23 Oct 2026, 20:208,063+74
20 Oct 2026, 16:497,989+10
17 Oct 2026, 11:117,979+6
14 Oct 2026, 21:477,973+14
11 Oct 2026, 05:187,959+34
5 Oct 2026, 00:577,925+31
25 Sept 2026, 18:367,894+71
17 Sept 2026, 10:577,823+20
13 Sept 2026, 13:577,803+11
9 Sept 2026, 17:597,792+36
4 Sept 2026, 20:027,756+33
31 Aug 2026, 19:177,723+39
28 Aug 2026, 13:287,684first reading

Engagement

66 posts held, back to 26 June 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 47 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
56.9%
avg views ÷ 8,285 subscribers
Avg views / post
4,710
18 posts measured
Reaction rate
0.617%
reactions ÷ views · ER floor
Posts in window
18
of 66 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 16 November 2026
Posts held66 (26 June 2026 – 16 November 2026)
Views total84,810
Reactions total523
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken18 Nov 2026, 03:06 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.

What this channel posts

Photos
389
Videos
14
Links
405

Lifetime counters from Telegram’s own channel header, read 18 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
26s
Average length
26s

Measured directly from 1 video 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

1,443 reactions across 63 posts, in 17 distinct kinds. The most used accounts for 36.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥53236.9%
custom 537331140509093899627018.7%
😁18713.0%
👍15110.5%
❤‍🔥765.27%
custom 5373163031150732302604.16%
😈292.01%
custom 5346135098309748287281.94%
custom 5240001719076668815221.52%
custom 5370774720096509791201.39%
custom 5240142636953640660151.04%
💅120.832%
custom 5300859949667072567110.762%
🍌110.762%
custom 5301285482141858441100.693%
🤔80.554%
👾10.069%

Custom emoji. 8 of the rows above are 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 are Telegram’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 66 of the 66 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 1,514 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 66 most recent posts we hold, published 26 June 2026 to 16 November 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
19
across the posts below
Posts paid on
8
of 66 we hold a reading for · 12%
Most on one post
10
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @P0x3k_1N73LL1G3NC3. 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 66 most recent posts we hold for this entry, published 26 June 2026 to 16 November 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.

Advertising

Ad load
4.55%
3 of 66 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
3,580
over 3 measured posts
Median views · rest
4,350
over 63 measured posts

An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.

This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.

Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.

Measured over the 66 most recent posts we hold, published 26 June 2026 to 16 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.

Recent posts

Telegram’s own ‘edited’ marker: 1 of 18 posts held from the last 30 days (5.56%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

16 Nov 2026, 04:16 UTC≈2,280 views29 reactionsread 18 November 2026
Photo

TrustFall - CVE-2026-88235: Windows TrustedInstaller Privilege Escalation Any local user can tamper with the file system and the registry as SYSTEM and achieve local privilege escalation.

🔥18custom 53731630311507323028👍3

12 Nov 2026, 15:12 UTC≈3,840 views33 reactionsread 18 November 2026
Photo

Dumping Kerberos TGTs with Microsoft’s own signed binary –klist & –klist-dump added to NetExec’s SMB & WinRM protocols. No LSASS dump, no scheduled task as the interactive user. Just the built-in klist.exe.

🔥21custom 53733114050909389965❤‍🔥4custom 53008599496670725672👍1

11 Nov 2026, 14:41 UTC≈3,420 views32 reactionsread 18 November 2026
Photo

They say I sometimes go too far in my pentest engagements… Boost channel

😁24custom 53012854821418584414🔥3👾1

11 Nov 2026, 10:00 UTC≈3,560 views27 reactionsread 18 November 2026
Photo

SignDrop Windows Common Log FileSystem Authentication 0day Local Privilege Escalation Vulnerability

🔥16custom 53733114050909389966❤‍🔥2👍2custom 52401426369536406601

6 Nov 2026, 04:19 UTC≈4,860 views29 reactionsread 18 November 2026
Photo

sshhole https://nebusec.ai/research/musl-openssh-star-hash/ A 257-character wrong password can get attackers into accounts that aren't supposed to accept passwords. No password cracking needed. Fix: Update OpenSSH and restart sshd, or set PasswordAuthentication no.

😈12👍9custom 53731630311507323025😁1custom 52400017190766688151custom 53461350983097482871

4 Nov 2026, 16:06 UTC≈4,630 views24 reactionsread 18 November 2026
Photo

CVE-2026-97798 LPE in the Windows Error Reporting (WER) Time Travel Debugging path. An unprivileged caller can preserve attacker-controlled command-line syntax across the WER privilege boundary. The elevated collector later concatenates that input into a TTTracer.exe command line without preserving argument boundaries. Injected -out and -launch switches are therefore interpreted by the TTD recorder as recorder optio…

custom 537331140509093899618👍3🔥3

4 Nov 2026, 16:06 UTC≈3,870 views14 reactionsread 18 November 2026
Photo

CVE-2026-42980 A Windows kernel WMI integer-underflow vulnerability that can be exploited for local privilege escalation to NT AUTHORITY\SYSTEM Blog: https://blog.grunt.ar/bin-exploitation/binary-gecko-academy/cve-2026-42980-wmi-underflow-en/

👍8🔥4❤‍🔥2

2 Nov 2026, 04:10 UTC≈4,680 views14 reactionsread 18 November 2026
Photo

BeyondTrust Remote Support File Upload to RCE metasploit module (CVE-2026-102764) An anonymous attacker can forge the MRS local router alias and invoke the appliance-side thin worker's native file-transfer service. This module uploads a PHP payload into the site's public directory and requests its extensionless URL. PHP and Unix command payloads execute as the site user. Tested on Remote Support 24.1.2; Blog: Rapid…

👍6🔥5🍌2😈1

30 Oct 2026, 05:33 UTC≈4,460 views46 reactionsread 18 November 2026
Photo

⚡️Цифровой рубль не пострадал 📢 Пездуза

😁38❤‍🔥5custom 52401426369536406603

30 Oct 2026, 04:14 UTC≈4,270 views27 reactionsread 18 November 2026
Photo

I hope their key was 4, that would be such a fitting end to the week)

😁22custom 53731630311507323025

29 Oct 2026, 16:41 UTC≈5,890 views46 reactions1 Starread 18 November 2026
Photo

ReverseShell_2026_10.ps1 A new PowerShell reverse shell in the PSSW100AVB repository. 100% AV bypass (October 2026)

🔥25👍7❤‍🔥5custom 53731630311507323025custom 53461350983097482874

29 Oct 2026, 10:10 UTC≈6,610 views25 reactionsread 18 November 2026
Photo

📜 From RCE to camera credentials in Axis Camera Station During a penetration test, I exploited CVE-2025-30023 (insecure deserialization) chained with CVE-2025-30026 (authentication bypass) to get SYSTEM-level RCE on two Windows machines running Axis Camera Station on a factory. After that, I discovered CVE-2026-63286, a weak credential encryption scheme, which allowed me to decrypt all the camera credentials stored …

🔥17custom 53707747200965097913custom 53733114050909389963💅1😈1

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

Posts edited after publishing

@P0x3k_1N73LL1G3NC3 edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
18 August 2026
Most recent edit
18 August 2026

Forward network

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

“1N73LL1G3NC3” (@P0x3k_1N73LL1G3NC3), 8,285 subscribers as measured 17 November 2026. Telegram Register, tgregister.com/channel/P0x3k_1N73LL1G3NC3.

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.