Old friend

Channel
Gateway
@G4t3w4y
On this record: Growth · Engagement · What this channel posts · Advertising · Posts · Citations · Handles named that no longer answer · Cite this entry
413subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001472547228 |
|---|---|
| Type | Channel |
| Username | @G4t3w4y |
| Description | Not a Gatekeeper Uploads realizados atráves da Clara Lille. Regras: - Só é permitido documentação Técnica, livros, conteúdos relacionados a segurança da informação/TI em geral. - Todo o resto é expressamente proibido. Parceiros: https://t.me/Phantasm_Lab |
| Created | Between 1 April 2019 and 30 September 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/G4t3w4y |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 6 Aug 2026, 22:30 | 413 | no change |
| 6 Aug 2026, 22:24 | 413 | first reading |
Engagement
20 posts held, back to 1 February 2023 — 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 pageof 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 20 posts for this entry, the most recent from 18 July 2025. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈201
- Videos
- ≈20
- Links
- ≈1,820
Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Advertising
- Ad load
- 5.00%
- 1 of 20 posts carry an ad marker
- Regulatory tokens
- 0
- none — marked by hashtag only
- Median views · ads
- 390
- over 1 measured post
- Median views · rest
- 521
- over 19 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 20 most recent posts we hold, published 1 February 2023 to 18 July 2025. 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
helo
https://www.youtube.com/watch?v=kICh_d6tHQk&ab_channel=JamesScholz
#RedTeam | #SpecterOps | #Jira | #Atlassian | #confluence | #Paper | #Pentest | #Hacking Sowing Chaos and Reaping Rewards in Confluence and Jira Let me paint a picture for you. You’re on a red team operation, operating from your favorite C2, and have just landed on a user’s workstation. You decide to take a look at their DNS cache to get a list of internal resources the user has been browsing and as you look throug…
#Redteam | #Teams | #Microsoft | #Phishing | #SpearPhishing | #TeamsPhisher Advisory: IDOR in Microsoft Teams Allows for External Tenants to Introduce Malware Max Corbridge (@CorbridgeMax) and Tom Ellson (@tde_sec) of JUMPSEC’s Red Team recently discovered a vulnerability in the latest version of Microsoft Teams which allows for the possible introduction of malware into any organisations using Microsoft Teams in it…
#RedTeam | #Recon | #OSINT | #AvoidDetection | #NSA | #Post WALKING THE TIGHTROPE: MAXIMIZING INFORMATION GATHERING WHILE AVOIDING DETECTION FOR RED TEAMS “WE PUT THE TIME IN TO KNOW THAT NETWORK. WE PUT THE TIME IN TO KNOW IT BETTER THAN THE PEOPLE WHO DESIGNED IT AND THE PEOPLE WHO ARE SECURING IT. AND THAT’S THE BOTTOM LINE.” The concept of truly understanding a network can be applied to the commercial side of…
#Hacking | #Mobile | #Bank | #Pentesting | #Reversing | #BrokenAccessControl | #BAC [Hacking Banks] Broken Access Control Vulnerability in Banking application [PART I] This is the part I of the story about finding a critical Vulnerability in a banking mobile app that allows attackers to obtain full user information (Balance, transaction list), as well as the ability to transmit money with just the victim’s phone …
Photo, posted without a caption
Uncovering Windows Events https://posts.specterops.io/uncovering-windows-events-b4b9db7eac54
#CVE-2023-23397 | #MDSec | #Hacking | #Microsoft | #Outlook | #PrivEsc Exploiting CVE-2023-23397: Microsoft Outlook Elevation of Privilege Vulnerability Microsoft Office Outlook contains a privilege escalation vulnerability that allows for a NTLM Relay attack against another service to authenticate as the user. However, no specific details were provided on how to exploit the vulnerability. At MDSec, we’re contin…
https://www.justice.gov/usao-mdfl/pr/russian-malware-developer-arrested-and-extradited-united-states
https://github.com/ihebski/A-Red-Teamer-diaries
Showing the 12 most recent of 20 posts we hold for @G4t3w4y. 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
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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@G4t3w4y named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 1 post, 8 August 2026 – 8 August 2026
named in 1 post, 8 August 2026 – 8 August 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 6 August 2026 — this entry's latest reading, not the date you are reading this.
“Gateway” (@G4t3w4y), 413 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/G4t3w4y.
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.