Channel
@SliceForLifeee
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4,984subscribers
+866 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003801414164 |
|---|---|
| Type | Channel |
| Username | @SliceForLifeee |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/SliceForLifeee |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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, 10:39 | 4,984 | +93 |
| 11 Sept 2026, 21:20 | 4,891 | +197 |
| 7 Sept 2026, 14:57 | 4,694 | +243 |
| 2 Sept 2026, 12:34 | 4,451 | +65 |
| 30 Aug 2026, 10:04 | 4,386 | +51 |
| 27 Aug 2026, 05:42 | 4,335 | +23 |
| 24 Aug 2026, 07:23 | 4,312 | +44 |
| 20 Aug 2026, 11:58 | 4,268 | +21 |
| 17 Aug 2026, 11:26 | 4,247 | +43 |
| 14 Aug 2026, 07:23 | 4,204 | +76 |
| 10 Aug 2026, 20:32 | 4,128 | +9 |
| 7 Aug 2026, 19:40 | 4,119 | +1 |
| 7 Aug 2026, 19:02 | 4,118 | first reading |
33 posts held, back to 6 August 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 3 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 33 posts for this entry, the most recent from 8 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.
26 reactions across 12 posts, in 4 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 13 | 50.0% | |
| 😁 | 6 | 23.1% | |
| 🔥 | 5 | 19.2% | |
| 😭 | 2 | 7.69% |
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 13 of the 33 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 26 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 33 most recent posts we hold, published 6 August 2026 to 8 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.
🚨 ShinyHunters claims an unnamed company as a victim. The listing claims over 11.5 million records across Salesforce, ServiceNow, and Entra containing some customer and employee PII, along with 3.1 TB+ of internal corporate data.
🔥5❤1
If you support this forum... go fuck yourself. Amarutu Technology Ltd, which operates the DDoS protection and hosting provider KoDDOS, has been identified in European parliamentary and academic monitoring reports as infrastructure associated with significant levels of online abuse. Research examining network abuse has also flagged its autonomous system as a notable hosting provider linked to the distribution of child…
❤4
forum[.]exploit[.]in 89[.]39[.]149[.]156 🇷🇴 ASN: 19624 Organization: Data Room, Inc
❤1
IP Information for 89.39.149.156 ASN: 19624 ISP / Org: SERVERROOM - Data Room, Inc, US Country: RO Network Range: 89.39.149.0/24
❤1
!ip 89.39.149.156
❤1
‼️ Exploit Forum: Exploit[.]in: 198[.]144[.]121[.]93 🇳🇱 ASN: 206264 Organization: Amarutu Technology Ltd send[.]exploit[.]in: 195[.]206[.]181[.]20 🇬🇧 ASN: 25369 Organization: Hydra Communications Ltd notes[.]exploit[.]in 31[.]220[.]0[.]206 🇧🇿 ASN: 206264 Organization: Amarutu Technology Ltd
😭2❤1
https://x.com/BtcpayServer/status/2085865561137831938
🚨🇫🇷 AFPABox user data and administrator access allegedly leaked ⠀ A forum actor claims to have leaked data associated with AFPABox, a platform connected to AFPA, France’s national adult vocational training organization. The post also claims administrator access to the platform. ⠀ The leak allegedly includes 101 user records containing: ⠀ • First and last names • Positions and account statuses • User messages • Ages a…
🚨‼️🚨 URGENT 🚨‼️🚨 BTCPay Server disclosed Friday that a critical vulnerability is being actively exploited and urged users to update their servers to version 2.4.2 immediately, according to the project’s official X account. The team warned that user funds could be at risk, although it remains unclear how many servers have been compromised or whether any funds have been stolen. Users who cannot update immediately we…
I have added 8 forums to the Forums Status Monitoring section on the threat feed, that are currently being onboarded. Almost all of them are of the carding variety. CTRL+SHIFT+R to refresh the page. No dates as to completion, but you will know once done.
The Secret Market for Zero Day Exploits Video Credit: youtube.com/Vice
❤1
🚨 WordPress patches XSS2Shell flaw that could lead to server code execution CVE-2026-64638 is a CVSS 8.9 pre-authentication XSS vulnerability in the WordPress login screen. The XSS itself requires no account. Researchers at pwn.ai demonstrated how it can be chained against a logged-in administrator to reach PHP code execution after social engineering the admin into interacting with an attacker-controlled page. A s…
Showing the 12 most recent of 33 posts we hold for @SliceForLifeee. 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.
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.
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.
Names
Channels on the register whose handles appear in this channel's posts.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“🔪 That Dark Web Guy - Part 3 🔪” (@SliceForLifeee), 4,984 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/SliceForLifeee.
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.