Channel
@secharvester
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
9,847subscribers
+418 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001140606841 |
|---|---|
| Type | Channel |
| Username | @secharvester |
| Created | 25 May 2017 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/secharvester |
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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 19:18 | 9,847 | +46 |
| 11 Sept 2026, 22:20 | 9,801 | +59 |
| 7 Sept 2026, 12:21 | 9,742 | +60 |
| 2 Sept 2026, 05:52 | 9,682 | +18 |
| 29 Aug 2026, 21:24 | 9,664 | +37 |
| 26 Aug 2026, 20:34 | 9,627 | +49 |
| 23 Aug 2026, 15:13 | 9,578 | +39 |
| 19 Aug 2026, 15:33 | 9,539 | +18 |
| 16 Aug 2026, 17:52 | 9,521 | +20 |
| 13 Aug 2026, 06:37 | 9,501 | +37 |
| 10 Aug 2026, 11:30 | 9,464 | +26 |
| 7 Aug 2026, 10:45 | 9,438 | +9 |
| 6 Aug 2026, 14:21 | 9,429 | first reading |
142 posts held, back to 13 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 34 pages 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 142 posts for this entry, the most recent from 19 August 2026. An engagement rate over an empty window would be a number about nothing.
4 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 75.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 3 | 75.0% | |
| 🤡 | 1 | 25.0% |
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 3 of the 142 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 4 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 142 most recent posts we hold, published 13 June 2026 to 19 August 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.
fnprint: identify functions in stripped binaries by behavior (microexecution), training-free, cross-compiler https://github.com/1rhino2/fnprint: 1. it runs each function in a tiny emulator with made-up inputs, records the side effects it produces, and hashes that behavior into a fingerprint. 2. the point of doing it this way: byte signatures (FLIRT, FunctionID) break the moment code is recompiled, and CFG matchers (…
I breached a server distributing Trojan, Stealer, and cryptominer malware https://mensvr.com/reports/indigo-shark: 1. Independent investigation into malware and cyber crime, leveraging offensive, reverse, and counter-adversary skills. 2. Professional hunter with hands-on experience, leveraging skills in network forensics, malware and reverse engineering. 3. Currently pursuing a Bachelor’s degree in Cybersecurity at …
I breached a server distributing Trojan, Stealer, and cryptominer malware https://mensvr.com/reports/indigo-shark: 1. Independent investigation into malware and cyber crime, leveraging offensive, reverse, and counter-adversary skills. 2. Professional hunter with hands-on experience, leveraging skills in network forensics, malware and reverse engineering. 3. Currently pursuing a Bachelor’s degree in Cybersecurity at …
Hacking SAML with Claude Code https://oblique.security/blog/hacking-saml/: 1. I applied to Anthropicâs Cyber Verification Program to remove the guardrails on my account, and after being accepted, I had access to an Opus model that could write exploits fed by my research and prompting. 2. These other messages rarely get the kind of security attention the SAML Response does, and I found signature bypasses in twelve …
Graphing AWS Attack Paths in Bloodhound https://blog.n0pe-sled.com/2026/08/10/awshound-an-opensource-aws-opengraph-collector/: 1. A free, read-only collector that turns an AWS account or Organization into a BloodHound OpenGraph dataset, drawing edges only where an offline IAM evaluation resolves to Allow. 2. Once the offline policy evaluation creates all nodes and edges, BloodHound can leverage its built-in path fin…
Passwords stored in public Google Doc then showed up in search results https://www.theregister.com/security/2026/08/13/passwords-stored-in-public-google-doc-then-showed-up-in-search-results/5287028: 1. In a separate incident, Kostabi heard from a Pageloot customer, a mid-size retailer, whose QR codes were suddenly directing users to a competitor’s site. 2. After investigating, he found that a disgruntled ex-employee…
WebAssembly's wasm2c sandbox escape. An untrusted WebAssembly module breaks out of the generated C sandbox and executes an arbitrary shell command on the host. https://github.com/trustsig-eu/wasm2c-tableflip: 1. Read the blog: trustsig.eu/blog wasm_rt_allocate_funcref_table() in wasm2c/wasm-rt-impl-tableops.inc sets table->size from the module's declared element count and then ignores the result of calloc() . 2. Dar…
CRLF-Powered Desync Attacks: Beheading HTTP Streams https://portswigger.net/research/crlf-powered-desync-attacks: 1. After a few days of scanning, and by just applying the techniques outlined in Making HTTP header injection critical via response queue poisoning , we quickly found a domain where we could trigger RQP. 2. In the end, creating a fancy “Loading your profile” page gave us the 10 seconds we needed to trigg…
I escaped the WebAssembly's sandbox and got arbitrary shell execution on the host. https://trustsig.eu/blog/wasm2c-tableflip-unchecked-calloc/: 1. wasm2c sets a table's size from the element count the guest declared, then ignores whether the allocation succeeded. 2. Make it fail and every table index becomes an absolute address on the host. 3. Fraud tooling shouldn't punish real users, or ship their data overseas. …
Iran's Mabna Institute ran a 3-phase spearphishing campaign against university professors for a decade. The 50-page superseding indictment has more methodological detail than the press coverage suggests. https://kancelaria-skarbiec.pl/en/iran-mabna-institute-indictment-university-hack-22-countries/: 1. Table of Contents On August 18, 2026, federal prosecutors in the Southern District of New York unsealed a fourteen-…
US warns Siemens devices can be hacked amid fears Iran is breaching water plants https://www.reuters.com/world/us-warns-siemens-devices-can-be-hacked-amid-fears-iran-is-breaching-water-plants-2026-08-19/ @secharvester
Vulnerable AI infrastructure in the wild: 34 minutes to server compromise https://bitbison.io/blog/langflow-rce-exposure/: 1. This article documents how attackers exploited the flaw, which credentials they accessed, which payloads they deployed and how defenders can identify affected systems. 2. Because Langflow returned command output in validation responses, 29% of attacker IPs that achieved code execution receive…
Showing the 12 most recent of 142 posts we hold for @secharvester. 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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.
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.
This channel appears in 13 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Security Harvester” (@secharvester), 9,847 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/secharvester.
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.