Telegram RegisterThe public register of Telegram
Telegram profile photo for CIPHER Cybersec

Channel

CIPHER Cybersec

@cipher_attacks

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

466subscribers

-14 since we began measuring on 9 August 2026

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

Register entry

Telegram ID-1002841831132
TypeChannel
Username@cipher_attacks
CreatedBetween 1 June 2025 and 30 September 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live16 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 16 September 2026
On Telegramt.me/cipher_attacks

Topic

Technology — 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 21 September 2026 and assigned it the closest of 31 fixed categories, at 63% 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.

Growth

4664804739 August 2026 — 480 subscribers10 August 2026 — 480 subscribers24 August 2026 — 475 subscribers9 September 2026 — 469 subscribers16 September 2026 — 466 subscribers9 August 202616 September 2026
5 measurements spanning 38 days, net -14. 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 464–482 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Sept 2026, 02:39466-3
9 Sept 2026, 09:59469-6
24 Aug 2026, 21:24475-5
10 Aug 2026, 03:31480no change
9 Aug 2026, 06:30480first reading

Engagement

20 posts held, back to 27 June 2026the 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 28 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

59 reactions across 13 posts, in 4 distinct kinds. The most used accounts for 47.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍2847.5%
🔥1525.4%
👨‍💻1118.6%
🌚58.47%

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 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 59 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 27 June 2026 to 28 July 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.

Recent posts

28 Jul 2026, 13:39 UTC184 views4 reactionsread 9 August 2026

ስለጠፋሁ sorry አሁንም ትንሽ ልቆይ እችላለሁ for months ምናምን ብዙ ስራዎችን እየሰራሁ ስለሆነ ነው

🔥3👍1

19 Jul 2026, 18:32 UTC267 views3 reactionsread 9 August 2026

clude ai skills 14M /mnt/skills 9.3M /mnt/skills/examples 61K /mnt/skills/examples/algorithmic-art 19K /mnt/skills/examples/algorithmic-art.skill 18K /mnt/skills/examples/benepass-reimbursement 7.0K /mnt/skills/examples/benepass-reimbursement.skill 14K /mnt/skills/examples/brand-guidelines 5.5K /mnt/skills/examples/brand-guidelines.skill 16K /mnt/skills/examples/call-to-book 6.0K /mnt/skills/examples/call-to-book.ski

🔥3

18 Jul 2026, 17:37 UTC239 views4 reactionsread 9 August 2026

new update for akasha userbot .ai <text> → chat (with memmory) .ai (reply image) → analyze media like .img .ai (reply voice) → transcribe + respond .cls → clear this chat history .persona default → chill user .persona expert → deep technical .persona roast → savage mode .aim <example> → single image .aims <example> → gallery : up to 9 imgs ઊcipher attack

👍4

17 Jul 2026, 07:37 UTC234 viewsread 9 August 2026
File

image quality enhancer Requirements: pip install opencv-python numpy usage: python3 enhance_image.py <input_path> <output_path> [options] example: python3 enhance_image.py photo.png photo_enhanced.png --scale 4 --sharpen-fine 0.7 ઊcipher attacks

13 Jul 2026, 05:04 UTC252 views4 reactionsread 9 August 2026

so what’s the solution? ካላችሁ fight fire with fire. we need to build our own automation ነው:: ​I’ve already built mine, and I’ll be dropping some starter code soon to help you grasp the basics. from there, you take it and push it forward. ​ઊcipher attacks

👍4

13 Jul 2026, 04:49 UTC267 viewsread 9 August 2026

​◆ እሺ ለምንድን ነው እያላችሁ ነበር አይደል ? ወደ ረጅሙ ዝርዝር ሳንገባ ዋናውን እውነታ በጥቂቱ እንይ ። ብዙዎቻችን አሁንም bug ሪፖርት ለማድረግ የምንከተለው old method ነው፡ ➔ recon ➔ scan ➔ exploit ➔ maintaining access ➔ covering tracks... በዚህ መንገድ pro ለመሆን እንጥራለን። ነገር ግን አሁን ባለው level አዲስ የbug bounty ፕሮግራም በወጣ በ30 ሰከንዶች ውስጥ አብዛኞቹ ወሳኝ ክፍተቶች report ተደርገው ያልቃሉ። ምክንያቱም? modern automation ለፍጥነት እና ለብቃት ወሳኝ በመሆኑ ነው። • hunters 24/7 አውቶማቲክ በሆነ መንገድ የሚሰሩ bug hunter bot ዎችን በማዘ

12 Jul 2026, 06:06 UTC246 views5 reactionsread 9 August 2026

አብዛኛውን ግዜ bug Bounty ላይ የሆነ vulnerability አግኝታችሁ በስንት ልፋት ከዛ out of scope እና duplicate መባል የተለመደ ነው በተለይ አሁን አሁን በፊት ያን ያህልም የለም ነበር ግን ለምን ይመስላቹሀል ሁል ግዜ የምንቀደመው 🤔 እኛ ስላልፈጠንን ወይም እንደነሱ እውቀት ስለሌለን 😓 አይደለም እስኪ አስቡበት እና ችግሩን ከነ መፍትሄው ይዘን እንመጣለን. ઊcipher attacks

👍5

11 Jul 2026, 09:40 UTC248 views3 reactionsread 9 August 2026

kemre eko new eskezare how hack my ex tg mnamn neber ahun aserar tekeyrual mekeyer bcha ayidelem befetari mass bot new yemimeslut abezazachew 😁😁nggrachew norm new sayitay yemitalef gn rkew betam yihedalu ego new yeminekut bcha leza new enem ende energy tetekme yemseraw tayalachu bekrbu tlk neger new yemnseraw 😉

🌚3

11 Jul 2026, 09:36 UTC257 views7 reactionsread 9 August 2026

btw cyber security layi troll yimechegnal ena next bzu troll kelal yemimeslu gn betam yemiyasfelgunn negroch mnamn bcha mn kerto bedenb enmaralen abren bzu nger enseralen wanaw alamachn system bypass adrgo income or degmo wisdom mefter new yenanten idk gn yene yihe new ena abzagnawochachu yaleflagot yemetachu leave me mnm neger atbelugn malet beka abren new yemnmarew ene kenante yeteleye alawkm enem emokralehu enante

🔥6👍1

Showing the 12 most recent of 20 posts we hold for @cipher_attacks. 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.

Mentions

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.

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

“CIPHER Cybersec” (@cipher_attacks), 466 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/cipher_attacks.

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.