Channel
@hackalls
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
147subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001591026036 |
|---|---|
| Type | Channel |
| Username | @hackalls |
| Created | Between 1 August 2021 and 31 January 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/hackalls |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 20:31 | 147 | no change |
| 7 Aug 2026, 12:40 | 147 | first reading |
15 posts held, back to 14 October 2025 — 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 pageof 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 15 posts for this entry, the most recent from 9 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
2 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 50.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 1 | 50.0% | |
| 🔥 | 1 | 50.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 2 of the 15 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 2reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 14 October 2025 to 9 April 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.
EDR Bypass - Extraction of the SAM database with the forensic tool winpmem. The only disadvantage is that a large memory dump file is created, totaling 9GB, which is a problem to transfer to Kali, so it must be compressed before transferring
🔥1
VMkatz Without VMkatz, the traditional workflow looks like this: exfiltrate the entire VM disk or memory snapshot, mount it locally, install a full Windows analysis stack, load the snapshot into a debugger or use mimikatz on a booted copy, and manually piece together credentials from each VM - one at a time. Multiply that by a dozen VMs on the cluster and you are looking at days of bandwidth, tooling, and post-proce…
Каждое запланированное задание имеет это значение SD (Security Decrypt); при его удалении запланированное задание не будет отображаться на панели планировщика заданий. Здесь я создаю задание с именем "plink". А после удаления этого значения задание не будет видно
❤1
Во время проведения пентеста, в зависимости от типа полученного начального доступа, невозможно сразу определить, есть ли в сети FortiGate, который может прервать атаку. Вывод здесь заключается в том, что после получения доступа тестирование эксплойтов не должно быть первым шагом. Вместо этого необходимо сначала выполнить разведку сети, ищущую: 1. Порт 443 (веб-администрирование FortiGate) 2. Порт 10443 (доступ по SS…
Сбой при выполнении эксплойта в тесте во внутренней сети может произойти из-за работы IPS FortiGate. Когда он активен, IPS обнаруживает шаблоны, связанные с сигнатурами уязвимостей, и осуществляет сброс пакета, несущего вредоносную нагрузку, прерывая эксплуатацию еще до того, как полезная нагрузка будет выполнена на цели. Затем создается журнал, содержащий IP злоумышленника и CVE, который он пытался использовать.
记一个东西：机器不出网，有几种利用方法？（如何进一步横向） 情况A：允许udp或者ping出网，直接用DNS Beacon 情况B：NAT存在到机器SSH的映射，可以想办法拿到SSH登陆，SSH可以全双工当隧道 情况C：NAT只存在到web端口的映射，需要一个webshell做正向代理 上线CS案例： 记一次不出网环境下上线CS【实战案例】 CobaltStrike-一种特殊的不出网上线方式 相关项目： reGeorg，Neo-reGeorg Suo5 Chunk-Proxy 这里面想继续横向应该只能一路正向马Beacon connect，或者找到别的出网机器 这里大概也解释了很多文章所谓websocket隐蔽的原因，应该是针对这种隧道webshell，产生的日志少 想起来件有意思的事：一位大哥当时遇到了这种机器，让我上自研的linux马来解决问题，然而这压根不是马自己能解决的，只能让webshell做隧道
Can't use you favorite impacket tools in FAST armored domains ? Fear no more ! BreakFAST is a small utility to demonstrate how Kerberos FAST armoring can be bypassed without local access to LSASS! Check out the repo: https://github.com/monsieurPale/BreakFAST @IRCyberGuardians
CVE-2025-64446 - обход аутентификации FortiWeb Уязвимость обхода аутентификации в продукте FortiWeb от Fortinet. Скрипт отправляет специально сформированный HTTP-запрос на целевой сервер FortiWeb, чтобы проверить наличие уязвимости: при успехе создается новый административный пользователь с учетными данными. THREAD CHANNEL 🍭 THREAD SHOP
File, posted without a caption
File, posted without a caption
Надо чекнуть на листе
https://github.com/S3N4T0R-0X0/BEAR
Showing the 12 most recent of 15 posts we hold for @hackalls. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“hackalls” (@hackalls), 147 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/hackalls.
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.