Sharing ARTEX detection signature pack - from IOC w/playbook process https://ift.tt/9O5Xfdh Submitted November 13, 2026 at 04:38PM by mmd0xFF via reddit https://ift.tt/BVYOzRX

Channel
Netsec
@RNetsec
On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
8,048subscribers
+313 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 | -1001107873651 |
|---|---|
| Type | Channel |
| Username | @RNetsec |
| Description | This channel posts the feed from r/netsec. For any suggestions dm @streaak Donate to keep the bot running https://www.paypal.me/akhilgv |
| Created | 16 July 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 11 November 2026 |
| Measurements held | 27 |
| Confirmed unchanged | 1 time, most recently 11 November 2026 |
| On Telegram | t.me/RNetsec |
Topic
Hacking & security — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Nov 2026, 22:16 | 8,048 | +7 |
| 8 Nov 2026, 01:31 | 8,041 | +2 |
| 5 Nov 2026, 08:08 | 8,039 | -3 |
| 2 Nov 2026, 03:19 | 8,042 | +14 |
| 29 Oct 2026, 18:07 | 8,028 | +6 |
| 26 Oct 2026, 19:06 | 8,022 | -1 |
| 24 Oct 2026, 03:37 | 8,023 | +14 |
| 21 Oct 2026, 05:59 | 8,009 | +17 |
| 17 Oct 2026, 20:49 | 7,992 | +14 |
| 14 Oct 2026, 10:50 | 7,978 | +10 |
| 10 Oct 2026, 22:54 | 7,968 | +42 |
| 5 Oct 2026, 04:57 | 7,926 | +23 |
| 26 Sept 2026, 22:17 | 7,903 | +34 |
| 15 Sept 2026, 11:37 | 7,869 | +16 |
| 11 Sept 2026, 12:38 | 7,853 | +24 |
| 6 Sept 2026, 10:20 | 7,829 | +45 |
| 1 Sept 2026, 21:23 | 7,784 | +10 |
| 29 Aug 2026, 20:05 | 7,774 | +5 |
| 26 Aug 2026, 14:44 | 7,769 | +12 |
| 23 Aug 2026, 11:06 | 7,757 | first reading |
Engagement
164 posts held, back to 31 July 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 39 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 5.07%
- avg views ÷ 8,048 subscribers
- Avg views / post
- 408
- 65 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 65
- of 164 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.
| Window | Rolling 30 days · latest post in window 13 November 2026 |
|---|---|
| Posts held | 164 (31 July 2026 – 13 November 2026) |
| Views total | 26,521 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 13 Nov 2026, 14:31 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
- Links
- ≈23,800
Lifetime counters from Telegram’s own channel header, read 13 November 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.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 65 posts held from the last 30 days (0%) 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).
Massive ‘wfx-loot’ Campaign Probes Over 60,000 GitHub Repositories to Steal CI and Cloud Secrets https://ift.tt/mGu9QWt Submitted November 13, 2026 at 06:42AM by Much-Television-9449 via reddit https://ift.tt/hB54tfo
OWASP Top 10 Neocloud and AI Data Center Security Risks project released https://ift.tt/s8HtBZ5 Submitted November 13, 2026 at 04:28AM by Pale_Fly_2673 via reddit https://ift.tt/FNeuDdQ
JSON Schema References Considered Harmful https://ift.tt/ysMKJEr Submitted November 13, 2026 at 04:05AM by allacebeats via reddit https://ift.tt/WuZphGM
NvRoot (CVE-2026-47591) where in neocloud multi-tenant GPU environments, rent = root. Essentially it's a dirty page cache LPE using GPUs as catalyzer https://ift.tt/47NybkL Submitted November 12, 2026 at 10:39PM by ChrisAtStealthium via reddit https://ift.tt/mSNny19
prepared statements prevents SQLi. But it also helped me to exploit a 22 years old PostgreSQL 0-day RCE (CVE-2026-6460) https://ift.tt/12F5m7T Submitted November 12, 2026 at 09:51PM by wtfse via reddit https://ift.tt/0GOk2sF
Claude Code VSCode Plugin: Workspace Escape Via Misleading Permission Prompt https://ift.tt/BjOto7S Submitted November 12, 2026 at 07:48PM by ultrastrik3 via reddit https://ift.tt/Bzora4l
How we defended against an AI-driven ARTEX attack https://ift.tt/DrQM5yW Submitted November 12, 2026 at 07:06PM by Far_Ice2481 via reddit https://ift.tt/8Fyzpag
History of Password Cracking https://ift.tt/DzZMsc9 Submitted November 12, 2026 at 06:32AM by netmux via reddit https://ift.tt/ji4hSQU
Hide and Stream: Ambient Aircraft-DopplerGeolocation of Live Audio, and a Defense https://ift.tt/8CEH0Ly Submitted November 11, 2026 at 08:45PM by lymn via reddit https://ift.tt/Cevt145
Qlik Sense Servers Hit With PowerShell Reverse Shells; Attacker Server Holds ActiveMQ and Veeam Exploits https://ift.tt/BAdZTUa Submitted November 11, 2026 at 08:25PM by Much-Television-9449 via reddit https://ift.tt/5uPO3lQ
ScriptBlock Smuggling - AMSI Evasion https://ift.tt/8MZew4l Submitted November 11, 2026 at 08:03PM by netbiosX via reddit https://ift.tt/yaTojFP
Showing the 12 most recent of 164 posts we hold for @RNetsec. 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.
Mentions
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
@vxunderground · 52,872
Telegram ranks this channel #10 of 41 here — alongside 40 others — read 24 August 2026
@OffensiveTwitter · 21,334
Telegram ranks this channel #12 of 53 here — alongside 52 others — read 25 September 2026
@cybdetective · 28,057
Telegram ranks this channel #21 of 49 here — alongside 48 others — read 11 September 2026
@thehackernews · 165,587
Telegram ranks this channel #21 of 58 here — alongside 57 others — read 13 August 2026
@thebugbountyhunter · 52,192
Telegram ranks this channel #25 of 60 here — alongside 59 others — read 25 August 2026
@cibsecurity · 29,268
Telegram ranks this channel #30 of 58 here — alongside 57 others — read 10 September 2026
@cloudandcybersecurity · 21,709
Telegram ranks this channel #40 of 62 here — alongside 61 others — read 22 September 2026
@Cyber_Security_Channel · 57,300
Telegram ranks this channel #42 of 71 here — alongside 70 others — read 23 August 2026
@the_block_crypto · 24,288
Telegram ranks this channel #50 of 87 here — alongside 86 others — read 15 September 2026
@github_repos · 28,188
Telegram ranks this channel #65 of 76 here — alongside 75 others — read 11 September 2026
This channel appears in 10 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 11 November 2026 — this entry's latest reading, not the date you are reading this.
“Netsec” (@RNetsec), 8,048 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/RNetsec.
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.