Telegram RegisterThe public register of Telegram
Telegram profile photo for Agentic Offense

Channel

Agentic Offense

@agenticoffense

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

6subscribers

+5 since we began measuring on 31 August 2026

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

Register entry

Telegram ID-1004414381089
TypeChannel
Username@agenticoffense
Created23 July 2026 — measured — dated from the channel’s first post
First recorded31 August 2026
Last confirmed live18 November 2026
Measurements held6
Confirmed unchanged2 times, most recently 18 November 2026
On Telegramt.me/agenticoffense

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 3 October 2026 and assigned it the closest of 31 fixed categories, at 67% 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

163.531 August 2026 — 1 subscribers1 September 2026 — 1 subscribers2 October 2026 — 3 subscribers20 October 2026 — 4 subscribers3 November 2026 — 5 subscribers10 November 2026 — 6 subscribers31 August 202610 November 2026
6 measurements spanning 71 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 0–7 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
10 Nov 2026, 09:506+1
3 Nov 2026, 10:305+1
20 Oct 2026, 10:364+1
2 Oct 2026, 21:363+2
1 Sept 2026, 02:171no change
31 Aug 2026, 03:301first reading

Engagement

10 posts held, back to 23 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 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 10 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

5 Aug 2026, 13:53 UTC2 viewsread 31 August 2026

My reduce layer still runs by hand. I have not put it on a schedule, and that is deliberate. This post is why. The rule I wrote into my own spec: the loop exits on real tool output, never on the agent's transcript claim. An agent that reports "reproduced" without the tool firing is the whole problem in one line. Mine is a reproduction gate. A finding does not count when the agent says "possible SSRF". It counts whe…

3 Aug 2026, 13:06 UTC3 viewsread 31 August 2026

Auth is the hardest part of an autonomous hunting setup, and it fails silently. Most bugs live in the authenticated area. So your agent has to log in and stay logged in. This is where it quietly dies. Some programs refresh the OAuth token every 15 minutes, and the refresh dies if you log in from another place. A server-side change breaks your keep-alive. Now the bot finds nothing for three weeks and you think the ta…

31 Jul 2026, 14:11 UTC4 viewsread 31 August 2026

A lesson from Singularity, a hackbot by Reszo and JD that found about 60-80 solid bugs in six months: more LLMs in the chain work better than fewer. The instinct is to hard-code the phases, recon then hack then chain, and keep it lean. But accuracy went up when they added a boss LLM between the human and the worker. Its only job is to say "no, you missed X and Y, go back and work harder." Two agents I added to my c…

29 Jul 2026, 13:10 UTC4 viewsread 31 August 2026

Everyone worries about AI false positives in security work. You do not prompt your way out of them. You need an execution step that proves the bug before a human sees it. Sansec audited 5,000 Magento extensions with a 4-stage pipeline. The stage that matters is the third one. It starts a live Docker container and runs the agent's own curl PoC against it. If the PoC does not fire, it is not a finding. Their numbers:…

27 Jul 2026, 12:20 UTC4 viewsread 31 August 2026

The most common mistake with AI agents on source code: you load the whole repo into the context and ask the agent to find bugs. It does not work. The context fills with code that has nothing to do with your bug, and the model starts matching patterns in that noise. You get answers that look confident and are wrong. This failure has a name: logical dilution. The fix is boring. A bash script feeds one file at a time.…

23 Jul 2026, 18:53 UTCviews —

Agentic Offense pinned «Start here. I hunt bugs and audit contracts, and I build the AI-agent tooling that does the grunt work alongside me. This channel is that tooling in the open: how the machine is wired, what it costs per run, and the parts that quietly break. What you get…»

23 Jul 2026, 18:53 UTC4 viewsread 31 August 2026

Start here. I hunt bugs and audit contracts, and I build the AI-agent tooling that does the grunt work alongside me. This channel is that tooling in the open: how the machine is wired, what it costs per run, and the parts that quietly break. What you get here: • how I wire agents for recon, source review, and validation • a technique per post, distilled to one thing you can actually use • field notes with real num…

23 Jul 2026, 18:32 UTC4 viewsread 31 August 2026

I hunt bugs with a machine I built out of AI agents. This channel is me showing the machine. Not tips. Not "10 prompts for hackers." The actual wiring: how the agents are split, where the loop verifies itself, what it costs per run, and the parts that quietly rot and cost me a week before I notice. One thing up front, because it's the whole thesis. The fully autonomous 24/7 hackbot that finds bugs while you sleep m…

Showing the 10 most recent of 10 posts we hold for @agenticoffense. 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.

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

“Agentic Offense” (@agenticoffense), 6 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/agenticoffense.

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.