Channel
@bugpoint
On this record: Growth · Engagement · Reactions · Posts · Cite this entry
969subscribers
-12 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001225901585 |
|---|---|
| Type | Channel |
| Username | @bugpoint |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 9 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 9 September 2026 |
| On Telegram | t.me/bugpoint |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 9 Sept 2026, 00:18 | 969 | -2 |
| 30 Aug 2026, 18:06 | 971 | -5 |
| 14 Aug 2026, 23:54 | 976 | -5 |
| 7 Aug 2026, 05:31 | 981 | no change |
| 7 Aug 2026, 05:24 | 981 | first reading |
20 posts held, back to 30 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
1 reaction across 1 post, in 1 kind.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 1 | 100.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 1 of the 20 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 1 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 30 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.
[Wii U/3DS/Switch] Improper bounds check in StationURL in all NEX clients leading to remote crash/RCE 🔹 Severity: Low 🔹 Weakness: Stack Overflow 🔹 Reported To: Nintendo 🔹 Reported By: jonbarrow 🔹 State: 🔵 Duplicate 🔹 Disclosed: August 7, 2026, 1:04am (UTC) 🐞 Source: HackerOne 👉 Read full report
Unauthenticated RCE in Taskcluster web-server via GraphQL filter argument (sift $where) 🔹 Severity: Critical | 💰 12,000 USD 🔹 Weakness: Code Injection 🔹 Reported To: Mozilla 🔹 Reported By: griffinf 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 3:50pm (UTC) 🐞 Source: HackerOne A vulnerability was discovered in the Taskcluster web-server that allowed unauthenticated remote code execution through the GraphQL filter…
curl Missing Sec-WebSocket-Accept Verification Enables MITM WebSocket Session Hijacking 🔹 Severity: No Rating 🔹 Weakness: Man-in-the-Middle 🔹 Reported To: curl 🔹 Reported By: kiyin 🔹 State: 🔴 N/A 🔹 Disclosed: August 5, 2026, 11:13am (UTC) 🐞 Source: HackerOne 👉 Read full report
`check_reserve_proof` counts duplicate entries: one output can inflate `total` 🔹 Severity: Medium 🔹 Weakness: Business Logic Errors 🔹 Reported To: Monero 🔹 Reported By: bebensap 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 10:23am (UTC) 🐞 Source: HackerOne A vulnerability was discovered in the `check_reserve_proof` function in the Monero wallet software. The vulnerability allowed duplicate entries in the reserv…
`check_reserve_proof` sums RingCT ECDH amounts without checking the output commitment 🔹 Severity: Medium 🔹 Weakness: Missing Required Cryptographic Step 🔹 Reported To: Monero 🔹 Reported By: bebensap 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 10:23am (UTC) 🐞 Source: HackerOne The `check_reserve_proof` function in the Monero codebase was found to sum RingCT ECDH amounts without checking the output commitment. T…
wallet-rpc crash via malformed /gettransactions response (empty txs → vector::front() in check_tx_key / check_tx_proof) 🔹 Severity: High 🔹 Weakness: NULL Pointer Dereference 🔹 Reported To: Monero 🔹 Reported By: bebensap 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 10:23am (UTC) 🐞 Source: HackerOne A vulnerability was discovered in the Monero wallet software that could cause the wallet-rpc process to crash when …
SpendProofV1 txid-substitution: get_spend_proof/check_spend_proof do not verify returned transaction hash 🔹 Severity: Medium 🔹 Weakness: Missing Required Cryptographic Step 🔹 Reported To: Monero 🔹 Reported By: bebensap 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 10:23am (UTC) 🐞 Source: HackerOne A vulnerability was discovered in the Monero project where the get_spend_proof and check_spend_proof functions do no…
wallet-rpc describe_transfer uses real_output_in_tx_index instead of real_output: cold-wallet pre-sign review shows wrong ring member 🔹 Severity: Medium 🔹 Weakness: Array Index Underflow 🔹 Reported To: Monero 🔹 Reported By: bebensap 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 10:23am (UTC) 🐞 Source: HackerOne The wallet-rpc method "describe_transfer" was found to use the wrong index when retrieving information…
`relay_tx` wallet-rpc skips `--restricted-rpc` guard and lets any caller corrupt wallet state via attacker-controlled `pending_tx` 🔹 Severity: Critical 🔹 Weakness: Improper Access Control - Generic 🔹 Reported To: Monero 🔹 Reported By: benisprlh 🔹 State: 🟢 Resolved 🔹 Disclosed: August 5, 2026, 5:05am (UTC) 🐞 Source: HackerOne The `relay_tx` wallet-RPC method in Monero was found to bypass the `--restricted-rpc` guard…
Heap use-after-free (write) in mev_forget_socket() via reentrant curl_easy_pause() — incomplete fix for CVE-2026-9080 🔹 Severity: Medium 🔹 Weakness: Use After Free 🔹 Reported To: curl 🔹 Reported By: juthawong 🔹 State: 🔴 N/A 🔹 Disclosed: August 4, 2026, 2:55pm (UTC) 🐞 Source: HackerOne 👉 Read full report
GitHub Retired UsernameTakeover From [aws/████████] 🔹 Severity: Low 🔹 Weakness: Inclusion of Functionality from Untrusted Control Sphere 🔹 Reported To: AWS VDP 🔹 Reported By: sh3d0w 🔹 State: 🟢 Resolved 🔹 Disclosed: August 3, 2026, 6:17pm (UTC) 🐞 Source: HackerOne A retired GitHub username was discovered to be unclaimed, allowing an attacker to register the username and create a repository with the same name as the…
Unauthenticated Path Traversal (LFI) via /custom-sounds/ when CustomSounds uses FileSystem storage 🔹 Severity: High 🔹 Weakness: Path Traversal 🔹 Reported To: Rocket.Chat 🔹 Reported By: howtoplay 🔹 State: 🟢 Resolved 🔹 Disclosed: August 3, 2026, 1:35pm (UTC) 🐞 Source: HackerOne 👉 Read full report
Showing the 12 most recent of 20 posts we hold for @bugpoint. 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.
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 9 September 2026 — this entry's latest reading, not the date you are reading this.
“Bugpoint” (@bugpoint), 969 subscribers as measured 9 September 2026. Telegram Register, tgregister.com/channel/bugpoint.
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.