Source Byte
前往频道在 Telegram
هشیار کسی باید کز عشق بپرهیزد وین طبع که من دارم با عقل نیامیزد Saadi Shirazi 187
显示更多8 509
订阅者
+824 小时
+527 天
+19030 天
正在加载数据
吸引订阅者
十一月 '2611月 '26
十一月 '26
+20
在0个频道中
十月 '26
+240
在0个频道中
Get PRO
九月 '26
+45
在0个频道中
Get PRO
八月 '26
+281
在2个频道中
Get PRO
七月 '26
+418
在5个频道中
Get PRO
六月 '26
+116
在1个频道中
Get PRO
五月 '26
+269
在6个频道中
Get PRO
四月 '26
+79
在0个频道中
Get PRO
三月 '26
+33
在1个频道中
Get PRO
二月 '26
+78
在2个频道中
Get PRO
一月 '26
+94
在1个频道中
Get PRO
十二月 '25
+266
在8个频道中
Get PRO
十一月 '25
+239
在3个频道中
Get PRO
十月 '25
+222
在2个频道中
Get PRO
九月 '25
+41
在0个频道中
Get PRO
八月 '25
+77
在2个频道中
Get PRO
七月 '25
+86
在1个频道中
Get PRO
六月 '25
+225
在7个频道中
Get PRO
五月 '25
+104
在7个频道中
Get PRO
四月 '25
+114
在2个频道中
Get PRO
三月 '25
+69
在2个频道中
Get PRO
二月 '25
+31
在0个频道中
Get PRO
一月 '25
+132
在0个频道中
Get PRO
十二月 '24
+256
在3个频道中
Get PRO
十一月 '24
+867
在1个频道中
Get PRO
十月 '24
+858
在1个频道中
Get PRO
九月 '24
+661
在1个频道中
Get PRO
八月 '24
+702
在3个频道中
Get PRO
七月 '24
+512
在16个频道中
Get PRO
六月 '24
+631
在5个频道中
Get PRO
五月 '24
+391
在8个频道中
Get PRO
四月 '24
+543
在4个频道中
Get PRO
三月 '24
+747
在6个频道中
Get PRO
二月 '24
+328
在2个频道中
Get PRO
一月 '24
+414
在1个频道中
Get PRO
十二月 '23
+376
在1个频道中
Get PRO
十一月 '23
+19
在0个频道中
Get PRO
十月 '23
+112
在0个频道中
Get PRO
九月 '23
+44
在0个频道中
Get PRO
八月 '23
+13
在0个频道中
Get PRO
七月 '23
+54
在0个频道中
Get PRO
六月 '23
+17
在0个频道中
Get PRO
五月 '23
+4
在0个频道中
Get PRO
四月 '23
+18
在0个频道中
Get PRO
三月 '23
+12
在0个频道中
Get PRO
二月 '23
+7
在0个频道中
Get PRO
一月 '23
+10
在0个频道中
Get PRO
十二月 '22
+8
在0个频道中
Get PRO
十一月 '22
+32
在0个频道中
Get PRO
十月 '22
+36
在0个频道中
Get PRO
九月 '22
+18
在0个频道中
Get PRO
八月 '22
+37
在0个频道中
Get PRO
七月 '22
+435
在0个频道中
| 日期 | 订阅者增长 | 提及 | 频道 | |
| 03 十一月 | +1 | |||
| 02 十一月 | +8 | |||
| 01 十一月 | +11 |
频道帖子
Seems someone wrote a SPL hunting rule for VMware Vcenter 🙄
VMware docs :
The ESXi hypervisor is a specialized, purpose-built solution, similar to a network router’s firmware. While this approach has several advantages, it also makes ESXi unable to run “off-the-shelf” software, including security tools, designed for general-purpose operating systems as the ESXi runtime environment is dissimilar to other operating systems.
| 2 |  没有文字... | 752 |
| 3 | How We Claimed a Pre-Bedrock Optimism Withdrawal
Link: https://medium.com/coinsbench/how-we-claimed-a-pre-bedrock-optimism-withdrawal-4d1df1ba017f | 1 025 |
| 4 | #Research
#cryptography
"Randomness-Anchored Runtime Discovery of Cryptographic Operations on Linux Using eBPF",
Oct 2026.
]-> https://github.com/yulim4hyoung/ebpf-pqc-runtime-discovery
// This work presents a runtime cryptographic discovery system for Linux, built on eBPF user-space probes, that detects classical and post-quantum operations as they execute | 2 287 |
| 5 | I’m pleased to share the Patchwork CTI Framework v0.7.1, now publicly available for community review.
Patchwork began as personal documentation, a way to connect the useful pieces of different CTI approaches. It has grown into a platform-independent framework for structuring observations, tracking adversaries, and sharing intelligence while preserving evidence, uncertainty, and assessment history. It brings together published approaches from CERT-EU, Mandiant/Google Threat Intelligence, Palo Alto Networks Unit 42, CISA, and OASIS STIX 2.1, documenting both what it adopts and where it deliberately differs.
The framework covers:
- Activity clusters, attribution tiers, and adversary naming.
- Confidence, source grading, and provenance.
- Classification, sharing rules, and STIX 2.1 serialization.
- Report templates, worked examples, and documentation tools.
A central design principle: stronger attribution should build on earlier assessments, not erase them.
We’re also developing a compatible threat-intelligence platform. That work is ongoing, and adopting the framework does not require using our platform.
This is a community-review draft, not a final standard. I’d welcome feedback from CTI analysts, researchers, CERT/CSIRT teams, and platform builders, especially on practical adoption, difficult attribution cases, and assumptions that deserve challenging.
Explore the framework and join the discussion:
https://github.com/CTI-Center/PatchWork
#CTI | 2 401 |
| 6 | bullshit
don't waste your time
#T | 2 201 |
| 7 | #Tech_book
#Offensive_security
#Red_Team_Tactics
"Red Team Engineering: The Art of Building Offensive Tools and Infrastructure", 2026.
]-> Various course materials, scripts, and configurations | 2 016 |
| 8 |  My New Blog Post
Evading Sysmon Dns Monitoring In 2026 | binary-win
DNSevade : https://github.com/binary-win/DNSevade.git
Sysmon gets its DNS telemetry from the Microsoft-Windows-DNS-Client ETW provider.
Let's hide in plain sight.
#sysmon #bypass
Your Notes are HERE | 1 871 |
| 9 | We were able to identify 6 Iran related underground activity , but yet shared POC of "JumpJump" vpn incident is unknown to us. It will be very helpful to help us cluster this activity by sending more details in our channel DM :)
also you don't need to pay for VPN !!!
Unredacted group provide high quality free solutions to anyone who need free access to internet :)
Try it now :
https://unredacted.org/blog/2026/07/internet-freedom-is-here-freesocks-v2/ | 2 344 |
| 10 | Building Something EDR-like with Rust×eBPF
https://speakerdeck.com/sunlife3/rustxebpf-de-edr-ppoi-mono-o-tsukuru | 1 949 |
| 11 | Hi
anyone an help me access t00ls.net ?
appreciate your time :) | 284 |
| 12 |  https://x.com/WuBlockchain/status/2090396627257503764 | 2 102 |
| 13 |  cool platform, don' miss it :) | 2 021 |
| 14 | Route of Root: Bring a "DoS only" bug to LPE and bypass the existing patch to win $10,500 in kernelCTF
#CVE-2023-2156 (“Route of Death”) is a Linux kernel vulnerability that was believed to only lead to a DoS attack, and was considered patched in April 2023. However, Nebula Security discovered a bypass of the patch and found that it is actually exploitable and can lead to LPE on any Linux distribution that has IPv6 and namespaces enabled. This writeup covers the technical details of the exploit.
https://nebusec.ai/research/cve-2026-43501-route-of-root/ | 2 342 |
| 15 |  You don’t always need to go for the hardest approach. Sometimes, you just need to understand what you actually need and choose the right path.
As you know, LSASS is heavily monitored and protected nowadays, so getting a dump from it isn’t as straightforward as it used to be.
So instead of getting stuck on LSASS and trying to bypass every protection around it, why not look at other options?
If the goal is to obtain local account credential material, SAM might be enough for what we need.
The point is simple: choose the technique based on the objective, not based on how complicated it is.
#EDR #SentinelOne | 1 654 |
| 16 |  没有文字... | 2 259 |
| 17 |  没有文字... | 2 053 |
| 18 |  https://github.com/FSECDEV/LEAKSFORUMS/blob/main/README.md | 2 412 |
| 19 |  i will waste my holiday on this 😂 | 1 907 |
| 20 | +4 Breached_Forums_Private_Messages.rar | 2 036 |
