Telegram RegisterThe public register of Telegram
Telegram profile photo for Project Sigma - Cyber Security From Zero

Channel

Project Sigma - Cyber Security From Zero

@ProjectSigma_CSFZ

On this record: Topic · Observations · Channels linked by matching posts · Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

493subscribers

+102 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001228679612
TypeChannel
Username@ProjectSigma_CSFZ
CreatedBetween 1 March 2018 and 9 January 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live4 November 2026
Measurements held14
Confirmed unchanged1 time, most recently 4 November 2026
On Telegramt.me/ProjectSigma_CSFZ

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 51% 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 the other topics.

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 2 other registered channels. This entry also sits inside a group of 3 channels linked by matching posts, directly or through other channels in the group; two members of the group may share no posts with each other. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@ProjectSigma_AdvancedPT/24816 Feb 2021, 17:20 UTC@ProjectSigma_CSFZ/269 · this entry16 Feb 2021, 17:20 UTC1.00under a minute
@ProjectSigma_CSFZ/275 · this entry23 Nov 2023, 20:10 UTC@ProjectSigma_AdvancedPT/25423 Nov 2023, 20:10 UTC1.00under a minute
@ProjectSigma_CSFZ/264 · this entry8 Feb 2021, 13:44 UTC@ProjectSigma_Programming/1238 Feb 2021, 13:44 UTC1.00under a minute
@ProjectSigma_Programming/12419 Feb 2021, 17:05 UTC@ProjectSigma_CSFZ/270 · this entry19 Feb 2021, 17:05 UTC1.00under a minute
@ProjectSigma_CSFZ/275 · this entry23 Nov 2023, 20:10 UTC@ProjectSigma_Programming/12923 Nov 2023, 20:10 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@ProjectSigma_AdvancedPT12 (8/8 hand-verifiable sample passed)0.98under a minutethis entry (7–5)
@ProjectSigma_Programming9 (8/8 hand-verifiable sample passed)1.00under a minutethis entry (7–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. None of the 6 matches recorded here fall after that date, so for this entry we cannot say whether any of them carried a credit. The duplication is measured; the absence of attribution is not.

“Published first” means first in this corpus. We hold 14 comparable posts for this entry, running 20 January 2021 to 22 April 2024. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 3 channels, the one whose matching posts we hold earliest is @ProjectSigma_CSFZ — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the keys clone_mutual · clone_source, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 3 registered channels linked by matching posts, directly or through other channels in the group. This channel may share no posts with some of the channels listed below, and listed channels may share none with each other. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

3914934426 August 2026 — 391 subscribers6 August 2026 — 391 subscribers6 August 2026 — 392 subscribers14 August 2026 — 396 subscribers20 August 2026 — 401 subscribers28 August 2026 — 399 subscribers4 September 2026 — 407 subscribers13 September 2026 — 424 subscribers25 September 2026 — 441 subscribers6 October 2026 — 440 subscribers14 October 2026 — 444 subscribers20 October 2026 — 456 subscribers28 October 2026 — 473 subscribers4 November 2026 — 493 subscribers6 August 20264 November 2026
14 measurements spanning 90 days, net +102. 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 376–508 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
4 Nov 2026, 10:19493+20
28 Oct 2026, 01:37473+17
20 Oct 2026, 04:27456+12
14 Oct 2026, 03:37444+4
6 Oct 2026, 10:19440-1
25 Sept 2026, 22:40441+17
13 Sept 2026, 03:57424+17
4 Sept 2026, 21:19407+8
28 Aug 2026, 03:07399-2
20 Aug 2026, 16:12401+5
14 Aug 2026, 06:56396+4
6 Aug 2026, 22:31392+1
6 Aug 2026, 20:05391no change
6 Aug 2026, 17:52391first reading

Engagement

20 posts held, back to 9 January 2021 — 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 22 April 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

22 Apr 2024, 22:01 UTC≈2,250 viewsread 6 August 2026
Photo

🌲 تنبيه مهم للجميع 📣 🔍 ندعوكم الآن للانضمام إلى سلسلة تحدياتنا التقنية الجديدة. هذه التحديات ليست فقط فرصة لاختبار مهاراتكم، بل هي فرصة مثالية لتطوير القدرات العملية في مجالات مثل الأمن السيبراني وتطوير البرمجيات. إنها فرصتكم لكسب خبرات قيّمة، تعزيز فهمكم، والاستعداد لمواجهة تحديات العالم الحقيقي، خصوصًا إذا كنتم من الطلبة الجامعيين أو المهتمين بتطوير مهاراتكم التقنية. ✨ نرغب في سماع آرائكم: ما هي التحديات التقنية…

Signed ȘħλɖΘώ

22 Apr 2024, 22:01 UTC≈2,400 viewsread 6 August 2026

التعليقات في المنشور القناة الاساسية : https://t.me/Linux_Arabs/2207

Signed ȘħλɖΘώ

19 Feb 2024, 21:28 UTC≈1,740 viewsread 6 August 2026
Forwarded from @AnjjzArabsPhoto

👥 خدمة العملاء: العمود الفقري للأعمال في العصر الحديث 🚀 🎙 المقدمة: انضم إلينا في رحلة مفيدة لاكتشاف خدمة العملاء، حيث يشرح هذا المقال مفهوم وأهمية خدمة العملاء في الأعمال التجارية. 🌟 🔎 تسليط الضوء على المهارات: تعلم كيف تقدم خدمة عملاء ممتازة بمجموعة من المهارات والممارسات الفعالة. هل أنت مستعد للتميز؟ 💯 🖥 اقرأ المقالة الكاملة لتكتشف المزيد: 🌲 anjjz.com/ar/blog/customer-service 🖥 📎 مقالات قد تهمك : 1 • 2 • 3 • …

Signed ȘħλɖΘώ

26 Jan 2024, 22:44 UTC≈1,570 viewsread 6 August 2026
Photo

🔒 البرمجيات الضارة: ما هي وكيف تحمي نفسك؟ 🛡 💻 المقدمة: انضم إلينا في رحلة مثيرة لاكتشاف البرمجيات الضارة، حيث يكشف هذا المقال أسرار أنواع البرمجيات الضارة وكيف يمكن أن تهدد أمنك وخصوصيتك. 🚀 🌐 تسليط الضوء على التهديدات: اكتشف الأنواع الرئيسية للبرمجيات الضارة وكيف يمكنك حماية نفسك منها. هل أنت مستعد للتحدي؟ 👾 🌕 اقرأ المقالة الكاملة لتكتشف المزيد: 🌲 [https://anjjz.com/ar/blog/types-of-malware/] 🖥 📎 مقالات قد تهمك :…

Signed ȘħλɖΘώ

23 Nov 2023, 20:10 UTC≈1,500 viewsread 6 August 2026
Photo

✈️ كشف الأسرار: كيف يتم اختراق طائرات الدرونز؟ 🕵️‍♂️ 💻 المقدمة: استمتع برحلة مثيرة في عالم الدرونز، حيث يكشف هذا المقال أسرار تقنيات الاختراق وكيف يمكن للقراصنة الرقميين الوصول إلى هذه الطائرات المتطورة. 🚀 🌐 تسليط الضوء على التهديدات: استعراض أنواع الاختراق الذي قد تواجهه طائرات الدرونز، من التدخل الإلكتروني إلى الهجمات البرمجية الخبيثة. هل هناك مفاجآت تنتظرك؟ 👾 🌕 اقرأ المقالة الكاملة لتكتشف المزيد: 🌲 [anjjz.com/a…

Signed ȘħλɖΘώ

8 Jul 2021, 20:36 UTC≈2,930 viewsread 6 August 2026
Forwarded from @SHADOW_YEMEN

السلام عليكم متابعين قناتي تكنلوجيا المعلومات - أمن المعلومات .. اسعد الله ايامكم حبيت ابلغكم ان طوال الفتره غائب على النشر بسبب إختبارات الجامعة وان شاء الله اخر اختبار لي هو يوم الاثنين القادم ، وبإذن الله سوف استمر في تقديم كل ماهو مفيد في القناة ، وان شاء الله سوف افتتح قناة تخص تعلم لينكس رابط القناة : - @Linux_Arabic (الجروب التابع للقناة) - @Linux_Arabs (القناة) - لن تنتظروا كثيراً وشكراً لكم جميعاً 🧡. #Lin…

Signed ȘħλɖΘώ

30 Apr 2021, 22:38 UTCviews —

Project Sigma - Cyber Security From Zero pinned « دعنا نتشاجر ، نبكى ، نختلف ، نتخاصم .. نخطىء .. نتفق دعنا نفعل اى شىء وكل شىء الا الفراق ... 🎻♥️ ملاذ♥️.»

30 Apr 2021, 22:35 UTC≈2,880 viewsread 6 August 2026

دعنا نتشاجر ، نبكى ، نختلف ، نتخاصم .. نخطىء .. نتفق دعنا نفعل اى شىء وكل شىء الا الفراق ... 🎻♥️ ملاذ♥️.

Signed ȘħλɖΘώ

19 Feb 2021, 17:05 UTCviews —

Project Sigma - Cyber Security From Zero pinned «السلام عليكم .. سيتم دمج جميع قنوات Project Sigma مع القناة الرئيسية ستصبح القناة الوحيدة لنا هي https://t.me/ProjectSigmaTeam وكل شيء سيتم نشره عليها هذه القناة سيتم إلغاؤها ..»

19 Feb 2021, 17:05 UTC≈2,690 viewsread 6 August 2026

السلام عليكم .. سيتم دمج جميع قنوات Project Sigma مع القناة الرئيسية ستصبح القناة الوحيدة لنا هي https://t.me/ProjectSigmaTeam وكل شيء سيتم نشره عليها هذه القناة سيتم إلغاؤها ..

Signed Khalil Abbas

16 Feb 2021, 17:20 UTC≈2,300 viewsread 6 August 2026

ملاحظة : سبب فشل الاستغلال بعد اول محاولة هو ان الاستغلال التلقائي اكتشف نوع النظام واللغة بشكل خاطئ وقام بتجربة الاستغلال بالإعدادات الخاطئة فسبب ذلك تعطيل لبروتوكول smb وبعض خصائص النظام وأصبح يرفض أي اتصال تم حل المشكلة بإعادة تشغيل النظام #الخلاصة تأكد من الاعدادات الصحيحة اصدار حزمة الخدمة service pack واللغة لأن لديك محاولة واحدة فقط !

Signed Khalil Abbas

16 Feb 2021, 17:15 UTC≈1,920 viewsread 6 August 2026
Forwarded from @ProjectSigma_AdvancedPTVideo

#2 ضمن مجموعة التجارب على نظام ويندوز xp استهداف أنظمة ويندوز xp باستغلال ثغرة ms08_067_netapi على بروتوكول smb تطبيق عملي على VM

Signed Eng. Obaida Ismail

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

Forward network

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.

Mentions

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

“Project Sigma - Cyber Security From Zero” (@ProjectSigma_CSFZ), 493 subscribers as measured 4 November 2026. Telegram Register, tgregister.com/channel/ProjectSigma_CSFZ.

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.