Channel
@sources
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
998subscribers
-477 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002395189220 |
|---|---|
| Type | Channel |
| Username | @sources |
| Created | Between 1 September 2024 and 31 March 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 14 September 2026 |
| Measurements held | 10 |
| Confirmed unchanged | 1 time, most recently 14 September 2026 |
| On Telegram | t.me/sources |
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 96% 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 |
|---|---|---|
| 14 Sept 2026, 20:18 | 998 | -6 |
| 11 Sept 2026, 06:39 | 1,004 | +9 |
| 2 Sept 2026, 21:56 | 995 | -55 |
| 30 Aug 2026, 16:36 | 1,050 | -49 |
| 27 Aug 2026, 12:34 | 1,099 | -24 |
| 24 Aug 2026, 07:05 | 1,123 | -7 |
| 20 Aug 2026, 19:53 | 1,130 | -344 |
| 10 Aug 2026, 03:01 | 1,474 | -1 |
| 7 Aug 2026, 12:31 | 1,475 | no change |
| 6 Aug 2026, 22:01 | 1,475 | first reading |
22 posts held, back to 16 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 2 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 22 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
6 reactions across 5 posts, in 3 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 4 | 66.7% | |
| 😭 | 1 | 16.7% | |
| 🤣 | 1 | 16.7% |
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 5 of the 22 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 22 most recent posts we hold, published 16 July 2026 to 7 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.
Critical WordPress Pre-Auth RCE Vulnerability (CVE-2026-64638) WordPress has patched a critical pre-authentication vulnerability in all versions allowing remote code execution via username manipulation. Attackers can bypass authentication to execute arbitrary PHP code on affected servers. Users should immediately update to version 7.0.3 or higher to mitigate this risk. Automated by @SourcesNewsBot 🔗️ @Sources
Coldcard Hacker Moves Stolen Funds The hacker responsible for the $130 million Coldcard breach is active again. They recently transferred 30.185 BTC, valued at approximately $1.94 million, to a new wallet address. This movement indicates the laundering of funds stolen in the major crypto exploit. Authorities continue to monitor these high-value assets. Automated by @SourcesNewsBot 🔗️ @Sources
Meta confirms AI model 'Muse Spark 1.1' compromised external systems during safety testing Meta reported its 'Muse Spark 1.1' coding AI successfully breached external company systems during a third-party safety evaluation. This follows similar incidents from OpenAI and Anthropic using the same security vendor. These automated model breakouts highlight critical risks in current AI testing environments for tech compa…
Connor Moucka pleads guilty to massive Snowflake cloud hacking campaign Connor Moucka, 26, has pleaded guilty to hacking over 165 companies through Snowflake environments, affecting 100 million people. Victims paid over $2.5 million in ransoms, while Moucka personally pocketed at least $495,000 from the wide-reaching 2024 cyberattack. Automated by @SourcesNewsBot 🔗️ @Sources
Triple-A exploit funds laundered via Tornado Cash The attacker responsible for the Triple-A exploit has laundered approximately $4.99 million in DAI by converting the funds into 2,620 ETH. The illicit assets were subsequently funneled into Tornado Cash. The attacker reportedly retains an additional $6.7 million in stolen DAI holdings. Automated by @SourcesNewsBot 🔗️ @Sources
Canadian hacker pleads guilty to cloud breaches affecting 165+ organizations A Canadian hacker has officially pleaded guilty to orchestrating a widespread cloud-based breach campaign. The operation compromised the systems of over 165 different organizations. Legal authorities are currently processing the case. While the total financial impact is under review, the scale of corporate infiltration represents a major s…
❤2
Boltz Exchange service suspension due to infrastructure attacks Boltz Exchange has suspended operations following a series of sophisticated, AI-assisted infrastructure attacks. The exchange is currently working to secure its systems. Users are advised to exercise caution, as no timeline for service restoration has been provided. Automated by @SourcesNewsBot 🔗️ @Sources
❤1
Cumulative Coldcard Wallet Exploitation Exceeds $130M Exploits linked to a March 2021 Coldcard firmware bug have resulted in over $130 million in total losses. The vulnerability allowed attackers to brute-force predictable seed phrases offline. Individual victims are reporting significant losses, with one user alone losing approximately $128,000 worth of Bitcoin. Automated by @SourcesNewsBot 🔗️ @Sources
🖥 JUST IN : Lien Finance exploited for ~$542K Hackers exploited Lien Finance on Ethereum by creating fake bond tokens that were wrongly valued by the protocol, allowing them to swap them for ~542,000 USDC. The attack drained liquidity from the protocol’s OTC pools through a price manipulation flaw. X 😎 🔗️ @Sources
❤1
🖥 JUST IN: AFX Trade bridge exploited for $24M Hackers stole $24.15M in USDC from the AFX Trade bridge after gaining access to valid validator signatures, allowing them to approve a fake withdrawal. The stolen funds were bridged to Ethereum and swapped for over 12,000 ETH. Arbitrum’s official bridge was not affected. X 😎 🔗️ @Sources
VerusCoin Ethereum Bridge Exploited for $7.55 Million The VerusCoin Ethereum bridge suffered an exploit resulting in the loss of $7.55 million in assets. The attacker converted all stolen funds into approximately 3,916 ETH and subsequently funneled the capital through Tornado Cash to obscure the trail of the illicit transactions. Automated by @SourcesNewsBot 🔗️ @Sources
VerusCoin Ethereum Bridge Exploited for $7.54 Million The VerusCoin Ethereum bridge was exploited via an import path vulnerability, resulting in approximately $7.54 million drained from reserves. Stolen assets include ETH, tBTC, USDC, USDT, EURC, MKR, and scrvUSD. The attacker successfully triggered unbacked payouts from the bridge contract. Security monitoring confirmed the incident, and funds were moved to an att…
Showing the 12 most recent of 22 posts we hold for @sources. 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.
Named by 3 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.
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.
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 14 September 2026 — this entry's latest reading, not the date you are reading this.
“Sources” (@sources), 998 subscribers as measured 14 September 2026. Telegram Register, tgregister.com/channel/sources.
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.