Telegram RegisterThe public register of Telegram
Telegram profile photo for r_blueteamsec

Channel

r_blueteamsec

@r_blueteamsec

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

40subscribers

+5 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-1001639265061
TypeChannel
Username@r_blueteamsec
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded10 August 2026
Last confirmed live4 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 4 September 2026
On Telegramt.me/r_blueteamsec

Growth

354037.57 August 2026 — 35 subscribers10 August 2026 — 35 subscribers14 August 2026 — 37 subscribers21 August 2026 — 38 subscribers28 August 2026 — 39 subscribers4 September 2026 — 40 subscribers7 August 20264 September 2026
6 measurements spanning 28 days, net +5. 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 34–41 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Sept 2026, 07:1840+1
28 Aug 2026, 21:1239+1
21 Aug 2026, 06:5738+1
14 Aug 2026, 09:3737+2
10 Aug 2026, 23:1635no change
7 Aug 2026, 04:0435first reading

Engagement

20 posts held, back to 22 July 2026the 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.

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 30 July 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

30 Jul 2026, 12:18 UTC8 viewsread 10 August 2026

Cleaning Out Inboxes: TA488 Comes for Outlook with Another Half-Click Exploit https://www.proofpoint.com/us/blog/threat-insight/cleaning-out-inboxes-ta488-comes-outlook-another-half-click-exploit https://redd.it/1vajhao @r_blueteamsec

28 Jul 2026, 03:19 UTC8 viewsread 10 August 2026

The SID that wasn’t there: bypassing KB5014754 to Domain Admin on a fully patched AD CS https://0xmaz.me/posts/certsrv-id-cmc-addExtensions-KB5014754-bypass/ https://redd.it/1v896ql @r_blueteamsec

26 Jul 2026, 06:18 UTC7 viewsread 10 August 2026

CTO at NCSC Summary: week ending July 26th https://ctoatncsc.substack.com/p/cto-at-ncsc-summary-week-ending-july-e89 https://redd.it/1v66ku8 @r_blueteamsec

25 Jul 2026, 05:18 UTC6 viewsread 10 August 2026

What I Learned from Sitting in on a Scattered Spider Sentencing https://www.aitmfeed.com/blog/blog-1/what-i-learned-from-sitting-in-on-a-scattered-spider-sentencing-14 https://redd.it/1v5ezg2 @r_blueteamsec

25 Jul 2026, 02:18 UTC4 viewsread 10 August 2026

Reverse Engineering Windows Data Deduplication: From Research to an Open-Source Recovery Tool Hi everyone, I've been researching Windows Data Deduplication and built DedupInspector, an open-source tool for offline reconstruction of deduplicated files from the Chunk Store. I'd love to hear your feedback, suggestions, or testing results. 📖 Research: https://7h3kn0w3r.github.io/blog/windows-data-deduplication/ GitH

24 Jul 2026, 19:18 UTC5 viewsread 10 August 2026

Chaos ransomware's msaRAT: Living off the browser to build a covert C2 channel https://blog.talosintelligence.com/chaos-msarat-living-off-the-browser-to-build-covert-c2-channel/ https://redd.it/1v5fkkz @r_blueteamsec

24 Jul 2026, 12:18 UTC7 viewsread 10 August 2026

A new extortion cocktail: office printers, small ransoms, and BitLocker https://securelist.com/new-extortion-scheme-printers-bitlocker/120718/ https://redd.it/1v53jka @r_blueteamsec

24 Jul 2026, 09:18 UTC8 viewsread 10 August 2026

JadeProx: Tracing a China-nexus Operation Through an OPSEC Mistake https://www.group-ib.com/blog/jadeprox-china-nexus-triback-loader/ https://redd.it/1v53m2x @r_blueteamsec

24 Jul 2026, 04:18 UTC7 viewsread 10 August 2026

📢 NEW GUIDANCE AVAILABLE 📢 MT103 Messages and Financial Crime: Understanding Fraud, Money Laundering, and SWIFT Abuse SWIFT MT103 messages sit at the centre of global banking, making them important artefacts for investigators and attractive targets for criminals. Worryingly, the intelligence we collect at intel.coalitioncyber.com continues to identify exposed SWIFT messages, both genuine and fabricated, sitting in

24 Jul 2026, 00:18 UTC5 viewsread 10 August 2026

Thailand's Ministry of Finance Targeted With Hermes AI Agent Running Unattended https://hunt.io/blog/thailand-ministry-finance-targeted-with-hermes-ai-agent https://redd.it/1v4mkzb @r_blueteamsec

23 Jul 2026, 23:18 UTC4 viewsread 10 August 2026

Iran War Cyber Threat Landscape | A Midyear Assessment on What Matters https://www.sentinelone.com/labs/iran-war-cyber-threat-landscape-a-midyear-assessment-on-what-matters/ https://redd.it/1v4na6s @r_blueteamsec

23 Jul 2026, 15:18 UTC4 viewsread 10 August 2026

UK and partners expose Russian state-supported actors for new ‘zero-click’ phishing campaign targeting Western organisations https://www.ncsc.gov.uk/news/uk-and-partners-expose-russian-state-supported-actors-for-new-zero-click-phishing-campaign https://redd.it/1v4fzh5 @r_blueteamsec

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

Named by 5 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.

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

“r_blueteamsec” (@r_blueteamsec), 40 subscribers as measured 4 September 2026. Telegram Register, tgregister.com/channel/r_blueteamsec.

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.