Must-see41
自建 GitLab 暴露面直接命中,未认证即可 RCE,需立即核对版本与补丁状态。
RT @TheHackersNews: 🚨 CRITICAL: GitLab flaw (CVSS 10.0) affects 12 years of releases.
CVE-2026-110264 could allow unauthenticated remote code execution on self-managed servers.
Read - https://t.co/frrfCwYlgp
PoC 已落地即可复现,PHP 及其衍生自托管设备受影响面可直接验证。
PoCs for the critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619 are now available on Kitploit.
https://t.co/bM1CamIkVH
https://t.co/SGOtVbuX6M
#PHP #CyberSecurity
AI Agent 驱动攻击链的实战证据,并关联 ConnectWise 供应链事件。
RT @MsftSecIntel: The China state-aligned threat actor Storm-0940 used the agentic AI penetration testing framework ARTEX to automate attacks targeting hundreds of organizations globally across a broad range of industries. Microsoft Threat Intelligence assesses that Storm-0940 was responsible for the recently disclosed ConnectWise supply chain compromise of a multitenant application. https://t.co/VXovj0jI90
Our investigation found that Storm-0940's use of ARTEX accelerated the speed of compromised application abuse to authenticate to target environments through applications that had already been granted access, allowing the threat actor to operate without requiring an interactive user sign-in. AI-accelerated follow-on activity included reconnaissance, application credential changes, and attempts to modify privileges that could enable expanded or persistent access.
Read our blog for a detailed analysis and indicators of compromise (IOCs), along with Microsoft Defender detections, protection recommendations, and guidance on investigating service principal sign-ins and unexpected application credential or privilege changes.
PHP 部署面极广,默认配置即暴露,需立即清点版本并监控利用流量。
RT @0xpvee: it took two PHP zero-days to get me to post my first tweet haha
anyways, both are critical RCEs, meaning remote code execution with no login required.
with PHP this widespread, defenders should be: inventorying PHP versions, watching for exploitation attempts and patching asap
自建 GitLab 直接暴露代码与密钥,未认证即可攻击,需立即评估。
Gitlab2shell 😂
New unauthenticated RCE affecting gitlab
Found by @joaxcar https://t.co/v8Uk2Oj0Is
打过补丁也可能被绕过,修复验证不能只看版本号。
RT @N3mes1s: I can confirm that @pruvadev found a variant bypass to the patch. https://t.co/5U7zzj76KY
即使自身不跑 PHP,共享宿主上的邻居中招也会连带受害,多数 VPS 商未修补。
RT @PaulosYibelo: there's a real risk that a single PHP server will be exploited to infiltrate a guest OS somewhere, & from there, CVE-2026-99999 could be exploited to breach the host OS, leading to all other guest servers. So even if you don't run php, if some random customer of your host does, you are still going to be affected. This is esp concerning knowing most vps/compute providers still aren't patched.
可由私钥直接预计算伪造任意站点证书,波及全球信任链。
In 2008, Debian disclosed that a change intended to silence Valgrind warnings had broken OpenSSL's random number generator.
The change removed code that mixed entropy into its internal state, leaving the process ID as the only meaningful source of variability. Attackers could precompute the possible keys instead of breaking the cryptography.
In 2026, eight of eMudhra's intermediate CA private keys turned out to be:
4, 56, 66, 115, 155, 156, 230, 237.
现成工具即可在 Windows 服务账户上一步拿到 SYSTEM。
CoercedPotato — Windows local privilege escalation tool that abuses SeImpersonatePrivilege via MS-RPRN and MS-EFSR RPC coercion to execute commands as SYSTEM. https://t.co/tgS2nIp2Ts https://t.co/iKCZxXfICk
直指 LLM 集成服务的攻击面,自建 agent 部署需重查边界。
i think the opencode hack was a warning shot. if you're running any service that touches llms, expect to get pwned, act accordingly!
模型批量挖洞后,0day 首发归属与披露时效成新变量。
Everyone scrambling to claim PHP2Shell. Looks like a lot of collisions. It's something we've been talking about for a while now, new model drops, everyone scrambles to find 0days... model find 0day.. people rush for f4me. https://t.co/Fq24CjwlXJ
影响覆盖任意 PHP 应用,公开 PoC 已在流传,需按版本尽快核对补丁。
RT @sagitz_: Today we disclose PHP2Shell - remotely exploitable memory corruptions in PHP
WordPress pre-auth RCE: ✅
Drupal pre-auth RCE: ✅
Joomla pre-auth RCE: ✅
Remote memory disclosure of any PHP application: ✅
Read more ⬇️🧵 https://t.co/wVfy4kdHhz
给出实际利用态势,可用于判断补丁紧迫度而非只凭披露恐慌。
⚠️php2shell (CVE-2026-109618 and CVE-2026-109619) - we have so far not seen major exploit activity around either vulnerability.
Exploit attempts seem to be limited to public POCs released in the past 24 hours, which based on our testing have predominantly been inoperative.
Track php2shell exploitation on Defused 👉 https://t.co/iRDhHlDkep
触发点位于 OOM 与致命错误处理路径,与传统输入过滤防护无关。
RT @sagitz_: PHP2Shell (CVE-2026-109618 and CVE-2026-109619) are memory corruption issues in PHP’s internal error handling (out-of-memory, fatal errors).
We've demonstrated that these can be exploited to full RCE or Heartbleed-style memory disclosure, regardless of application logic https://t.co/wkK6GS7As3
只需服务端返回 Content-Encoding: br 即可触发,补丁版本已明确列出。
RT @julianor: While everyone’s patching PHP today, don't sleep on Node.js CVE-2026-111497 OOB write in the bundled Brotli decoder. Reachable via fetch(): a malicious server just replies
Content-Encoding: br.
Fixed in 26.12.1 / 24.22.1 / 22.23.4.
Update.
LLM 网关类组件被投毒,依赖它的自建 Agent 会直接带入恶意代码。
RT @y0n3uchy: 🚨 Confirmed LiteLLM PyPI package compromise… again. Will update details at:
https://t.co/AhkO05fVH5
PoC 落地后扫描与利用随即开始,暴露在公网的 PHP 服务需优先排查。
Exploit traffic started to flow in #php2shell https://t.co/rJroURX7rb
权威来源列明受影响与修复版本,是判断暴露面的第一手依据。
RT @HackingLZ: 👀
https://t.co/q21QbEPljO
升级目标版本在此确认,运维可照版本号直接安排更新。
RT @php_net: PHP 8.4.27 released - 89 fixes in 30 components, including security fixes (CVE-2026-109618, CVE-2026-109619).
Changelog + downloads: https://t.co/i0VF5tjG0x
自托管 LLM 网关高频依赖,锁定版本并排查该版本安装记录与出网行为。
ffs, litellm compromised again!
if you installed llitellm==1.107.0, good chance your environment is compromised
给出 CVE-2026-109618/109619 的实际暴露面数据,可对照自查优先级。
RT @virustotal: Two critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619), a leak before the patch and millions of PHP servers on the Internet. We used VirusTotal Internet Scanning to measure who is exposed, what they run and how to cut the window:
https://t.co/RgxlT3bCmr
展示 LLM 自动化漏洞挖掘的实际产出,并点名 OpenSSH 预认证面收窄点。
RT @chrisrohlf: Reducing the attack surface of deployed services and apps is a fundamental component of software that is secure by design. Earlier this year we tasked Claude with autonomously mapping and reducing the attack surface of 25 large and widely used OSS codebases. This blog post covers some of our methodology and a preview of the data we collected.
This research resulted in a significant reduction in OpenSSH pre-authentication attack surface (now fixed in 10.6). And over 500 findings where reachability could be reduced and configurations hardened to ensure security controls weren’t silently disabled.
https://t.co/8Iun038PNY
六个 TLS 中间 CA 私钥可恢复,能伪造任意域名的受信证书。
Let’s not forget about this certificate clusterfuck while everyone is busy with the PHP RCE news.
Almost at the same time, another serious security incident became public.
Eight intermediate CA certificates from eMudhra were found to use ridiculously weak private keys. We’re talking about P-384 keys where one private key was literally the number 4. FOUR!
Six of these were TLS CAs, allowing anyone to recover their private keys and potentially issue trusted certificates for arbitrary domains.
Major browsers have already blocked the affected CAs. But what about API clients, backend services, embedded devices, containers, and systems with outdated trust stores?
Many don’t enforce Certificate Transparency or check revocation. Some could remain vulnerable for years.
These weak keys have existed since April 2025. No confirmed malicious exploitation so far, but the implications are serious.
Don’t overlook this one while focusing on PHP.
Technical details and test endpoints:
https://t.co/6NiX0zsfNm
上游 8.5.4 未必存在可达路径,公开 PoC 的通用性存疑。
RT @UK_Daniel_Card: Testing the POCs in the lab with Claude, whilst drinking tea! (how 2026 of me :P /S cringe)
and.... we have some interesting and useful intel.....
exploitation of these CVEs doesn't appear trivial....
"Most likely why: the authors targeted a specific build (“Ubuntu php 8.5.4 profile-21”) with hard-coded struct offsets and a build-specific address delta. Vanilla upstream 8.5.4 either doesn’t carry that exact reachable path or the heap groom depends on that build’s allocator state. I’ll also be candid: this CVE pair is described in the PoCs themselves as leaked/pre-embargo/”presumed,” and I can’t independently verify it maps to a reproducible upstream bug."
#PHP
被滥用的 agent 框架不止一例,同类自托管架构存在共性攻击面。
Line up of other AI agent frameworks that are also powerful but get less attention as the headline grabbing ARTEX incidents.
可直接取回 PoC 在自有 PHP 环境验证是否真受影响。
https://t.co/hgmrKn5ohA
难道是真的? https://t.co/TsfG9P6YKN
可直接照抄的资产发现脚本,覆盖 CVE-2026-109618/109619 的排查
Two very useful posts on monitoring and hardening PHP services, plus an Nmap command to help find them in your environment:
1. Discovery with Nmap
Common and alternative web ports; HTTP headers that may expose PHP versions:
nmap -sT -sV --version-light -T4 --max-retries 1 --open -p 80,81,443,8000-8010,8080-8090,8181,8443,8880,8888,9000,9001,9080,9090,9443 --script http-headers --script-timeout 10s --script-args 'http-headers.path=/index.php,http-headers.useget=true' <target>
Look for X-Powered-By: PHP/.... Fast inventory check; hidden PHP deployments can be missed, and version banners don’t confirm vulnerability.
2. Huntress: Monitoring and detection
• Confirmed facts and remaining questions
• Suspicious PHP child processes, shells and downloaders
• Webshells and other post-exploitation activity
• My process-watcher for Linux process visibility
https://t.co/XLx8za50cZ
3. Vincent Schmalbach: Hardening and patching
• Temporary nginx/Apache filters and upload-progress settings
• WAF/origin bypass checks
• Package and backport verification
• PHP-FPM/worker restarts, container rebuilds
• Side effects and checks for compromise
https://t.co/30YfHmqIcR
Temporary measures are stopgaps. Prepare to apply the official fixes as soon as available.
第三方 Skill 人工审查可被静默绕过,注入手法可直接复用
RT @bquintero: How Some Malicious AI Skills Hide Instructions from Human Reviewers
* Whitespace padding
* HTML comments
* Invisible Unicode
https://t.co/b22Isbg62p
官方修复尚在准备,暴露在公网的 PHP 实例已在无补丁窗口内。
🔥Two critical PHP RCE vulnerabilities, 𝗖𝗩𝗘-𝟮𝟬𝟮𝟲-𝟭𝟬𝟵𝟲𝟭𝟴 𝗮𝗻𝗱 𝗖𝗩𝗘-𝟮𝟬𝟮𝟲-𝟭𝟬𝟵𝟲𝟭𝟵 (𝗖𝗩𝗦𝗦 𝟵.𝟮), 𝗵𝗮𝘃𝗲 𝗯𝗲𝗲𝗻 𝗱𝗶𝘀𝗰𝗹𝗼𝘀𝗲𝗱 𝗮𝗵𝗲𝗮𝗱 𝗼𝗳 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗹𝗲 𝗽𝗮𝘁𝗰𝗵𝗲𝘀. Emergency PHP security updates are being prepared, and affected versions are still being confirmed.
𝗙𝗼𝗿 𝗻𝗼𝘄, 𝘁𝗵𝗲 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝘆 𝗶𝘀 𝗰𝗹𝗲𝗮𝗿: 𝗶𝗱𝗲𝗻𝘁𝗶𝗳𝘆 𝗲𝘃𝗲𝗿𝘆 𝗶𝗻𝘁𝗲𝗿𝗻𝗲𝘁-𝗳𝗮𝗰𝗶𝗻𝗴 𝗣𝗛𝗣 𝗶𝗻𝘀𝘁𝗮𝗻𝗰𝗲, 𝗮𝘀𝘀𝗲𝘀𝘀 𝗲𝘅𝗽𝗼𝘀𝘂𝗿𝗲, 𝗮𝗻𝗱 𝗯𝗲 𝗿𝗲𝗮𝗱𝘆 𝘁𝗼 𝗽𝗮𝘁𝗰𝗵 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆 𝘄𝗵𝗲𝗻 𝗳𝗶𝘅𝗲𝘀 𝗯𝗲𝗰𝗼𝗺𝗲 𝗮𝘃𝗮𝗶𝗹𝗮𝗯𝗹𝗲. 𝗗𝗼𝗻’𝘁 𝘄𝗮𝗶𝘁 𝗳𝗼𝗿 𝗮 “𝗽𝗵𝗽𝟮𝘀𝗵𝗲𝗹𝗹” 𝗲𝘅𝗽𝗹𝗼𝗶𝘁𝗮𝘁𝗶𝗼𝗻 𝗰𝗮𝗺𝗽𝗮𝗶𝗴𝗻 𝘁𝗼 𝘀𝘁𝗮𝗿𝘁 𝗯𝗲𝗳𝗼𝗿𝗲 𝘁𝗮𝗸𝗶𝗻𝗴 𝗮𝗰𝘁𝗶𝗼𝗻.
https://t.co/JWWesPE0fU
#php2shell #vulnerabilitymanagement
改一行 php.ini 即可临时断链,补丁还需数小时到数天才能铺开。
RT @Kostastsale: A moron has released a POC early for php2shell so here is what you need to do:
If you’re on version prior to 8.2:
Edit php.ini: session.upload_progress.enabled = Off
Then reload php-fpm and restart apache
If you’re on later version:
Update (it’ll be available in a few hours)
In any case, the mitigation for the php.ini should work either way. Not sure if it’ll cover both vulns though so keep an eye on that. I’ll be reporting on follow up activity on windows as a target.
Good luck!
自托管 Agent 普遍缺通用沙箱,声明式策略与凭证注入可直接套用。
OpenShell v0.1.5 — Sandboxed runtime for autonomous AI agents with declarative YAML policies enforcing filesystem, network, and process constraints, plus endpoint-bound credential injection. https://t.co/9o8m2zJkMW https://t.co/6MJZxrXr7n
客户端仍信任该 CA 时,中间人可冒充银行等站点,影响面覆盖所有用户。
A stolen website key puts one site at risk. eMudhra’s weak CA keys could let attackers forge HTTPS certificates for any domain. If they intercept your connection and your client still trusts those CAs, they could impersonate your bank and read or modify traffic.
上传路径默认可达,利用思路已公开而官方暂无缓解措施,PHP 站点需立即评估。
RT @rina4_tot: More details about CVE-2026-109618 and
CVE-2026-109619, the PHP RCE.
Upload progress can serialize before basic RINT clears BG(serialize)
There is currently no possible mitigation.
See the screenshot below to understand how I got the UAF 😼 https://t.co/wdUjCP2hRa
披露前少有的系统梳理,可用于提前定位受影响 PHP 部署与暴露面。
RT @HuntressLabs: Ahead of tomorrow's disclosures, read our blog for an overview of what we know so far: https://t.co/3MTEUlPE5W
AI 辅助漏洞挖掘已规模化产出真实漏洞,攻防节奏与补丁压力将同步上升。
RT @oct0xor: Dr. Zhiniang Peng (@edwardzpeng) reveals how he discovered 200+ confirmed vulnerabilities in Microsoft Windows with the help of AI. The game has changed completely. 🤯 https://t.co/zN5xbKvpzj
AI 直接产出二进制使能力约束更难施加,对 AI 攻防边界的判断需重估。
刚开始接触生物学的时候,我经常想象原始海洋里的有机分子构成核糖核酸,然后诞生了最早的单细胞生物,单细胞生物又聚在一起变成黏糊糊的原始多细胞生物,最终一步一步演化出各种生灵。我也经常想,如果能在实验室里加速重现这一过程,完整观察整个生物演化史就好了。
刚开始接触计算机的时候,我想过一个问题:程序是从哪里来的?后来我知道了编译器,程序从编译器来的。编译器自然也是从其它编译器来的。那么最早的编译器是从哪里来的?后来我逐渐搞清楚了这个问题的答案。但偶尔还是会想一些相关的问题,比如:如果现在全世界的编译器都忽然消失,人类要怎么重建整套体系呢?
最近几年研究 AI 安全问题的时候,我经常想:如果只给予 AI 完成特定工作所需的工具,那么 AI 的能力是不是就会被限制住?是不是就可以阻止 AI 获得强大的网络入侵能力?
2026 年 2 月,我看到马斯克预测到年底 AI 就可以绕过编译过程直接创建二进制文件。当时我做了一些实验,发现虽然 AI 还不能创建完整可运行的程序,但已经可以生成正确的机器码片段了。到了 9 月,我再次实验,发现此时 AI 已经可以用直接创建二进制文件的形式输出不太复杂的程序了。
但用直接输出二进制文件的方式去写大型程序显然不是好的选择,即使能写出来,也难以维护。那么,是不是可以让 AI 重演现代编译器的诞生过程?就像重演从核糖核酸到哺乳动物的生物演化史?
下面这个视频里超级马里奥游戏就是从核糖核酸开始构建的。
AI 先是通过直接输出二进制的方式构建了一个 3584 字节的机器码装配器 A0。然后用 A0 生产了一个更类似汇编器的工具 A1。又用 AI 生产了最基础的 C 编译器 C0。再一步一步迭代,最终演化出了一个完整支持 C89 标准并部分支持 C99 标准的编译器。有了这个编译器,就可以写出超级马里奥游戏,或者是任何网络攻击程序。
对 AI 说:“要有光”,然后整个世界就一步一步诞生了。所以我把这个项目命名为 BitKindle。感兴趣可以测试一下:https://t.co/GN9onM4vTq
预告当天即公开可复现利用,PHP 站点暴露窗口极短。
php2shell
Tomorrow is a helluva day. https://t.co/M8ybQcrnlu
缓解项为单行 ini 配置,可立刻落地覆盖未打补丁的实例。
Temporaly mitigation
php.ini: session.upload_progress.enabled = Off
UPGRADE TO THE LATEST PHP after 2pm UTC
影响面覆盖绝大多数 PHP 部署,利用链正在成形。
5.6 Sol just found more UAF in core php and php-fpm. More CVEs coming soon.
To fix: codex -p "rewrite the app to anything but php". This is not a joke.
PHP 部署面极广,若默认安装即受影响,暴露规模远超单一应用。
RT @h4x0r_dz: if this affects the default installation of PHP
We are fucked up
CVE-2026-109618
CVE-2026-109619
PHP RCEs with a CVSS score of 10.0 ☠️
https://t.co/kr47MzTvIj https://t.co/NDq0mppHoT
官方公告是确认影响版本与修复范围的第一手来源。
https://t.co/3f1yfZH6d2
More155
分层载荷链条细节具体,检出率低,可据其补充 LNK 与 certutil 检测规则。
RT @nextronresearch: #Kimsuky (APT-C-55) is delivering persistent backdoors through multilingual LNK phishing lures
After reading the 360 Threat Intelligence Center's report on APT-C-55's multi-path delivery campaign, we found a cluster of nine related malicious LNK files submitted between September and October 2026, with detection ratios around 10-30 out of 60+ engines.
The LNK files execute a layered attack chain: base64-encoded batch scripts decoded via a renamed copy of certutil.exe, staging in C:\Users\Public, nircmd disguised as ntoskrnl.exe, and scheduled tasks running every 9 minutes for persistence. A parallel variant uses PowerShell with double hex-encoded payloads, and a third path poisons the open-source pybroker Python library as a supply chain attack.
Analysis & IOCs: https://t.co/QbhNDXUZvD
厘清模型/工具链威胁模型边界,判断同类“漏洞”是否值得投入修复。
Like, at the point where you import and run attacker python code here you have already executed arbitrary attacker controlled code? https://t.co/bbTHxcSB0U
This seems like a neat way to obfuscate some malicious code but I don’t see where it could be a vulnerability? By the time you’re running someone else’s regularizer you’re already running untrusted code and it could just tamper with the weights directly?
"unauthorized third party may have accessed encrypted environment variables"
GG
RT @filpizlo: It's all good y'all @meekaale made PHP memory safe
https://t.co/FJfBWwRbrx
RT @catc0n: lots of public poc being thrown, but no aslr bypasses. please, TAs, give us *tHe gOoD sHiT*
RT @HackingLZ: Something that gets lost in all these conversations is that there were years when a major 0day would drop and technical details were almost impossible to come by. Multiple people here would stay up for days reverse engineering the issue and stitching together a working PoC, not just to prove exploitation was possible, but to help defenders understand the actual risk, develop IoCs, build detections, and clean up compromised environments.
theres some pretty massive improvements you can make to deepinfer
but deepseek almost never merges PRs or maintains repos that they oss :/
签名不再是可信信号,白名单需按发布者证书而非签名状态校验。
@malwrhunterteam shared two MSI installers with this signer "SOPHISTICATED SOFTWARES (PTY) LTD"
The first is a rust remote shell
https://t.co/tUoOUV8j7N
The second is a tool which calls itself CrocoRAT:
https://t.co/YIKUVrSINt
We've seen CrocoRAT a few times 🧵
供应链windowsrat钓鱼
@SquiblydooBlog
source ↗
QUIC/HTTP3 覆盖面广,但披露措辞可疑,需先核实再动作。
RT @4A4133: Sorry everyone... We're announcing a 0-Day vuln in QUIC that allows anyone to remotely turn off a server running these libraries. I swear we didn't plan this.
https://t.co/fopoKsPulV
冷门 Win32 API 可绕常规调用链监控,适合本地验证检测覆盖。
Executing Shellcode with SetupIterateCabinetW
Credits:
@0xmrlowlevel https://t.co/CYUbxD6caO
shellcode绕过windowspoc
@Salsa12__
source ↗
在野利用早于公开披露,日志回溯的排查窗口需显著拉长。
Someone I know very well ran scans through old boxes and found traces of this PHP exploit going all the way back to 2022
But many people on this website prefer to believe that sophisticated nation states don’t have actual genius hackers and nothing is real until someone is blasting it out publicly for nerdpoints
漏洞研究产能与披露节奏被改变,防守方修复窗口被压缩。
gotta give it to openai and their sane daybreak program
heif heist by harsh
kvmescape by paulos
php2shell by lcfr
gitlab rces by joaxcar
chrome full chain by moyix
wordpress rce by hashkitten
all largely thanks to openai daybreak giving researchers access to gpt 5.6 sol. anthropic took the opposite approach, gatekeeping access, there is a lesson to be learned here
补充证书级 IOC,可直接用于签名者信任阻断规则。
In addition to this cert, we've also seen them using "JB Alpha Digital AB" and "1090 Fishing Mapp Oy"
The blogposts really have more indicators and information than I can fit in a tweet.
Damn PHP bug took out Bioware
RT @uid0sec: @Niki727189 @ryanaraine not embargo, the text says two independent findings reported to PHP same day by different companies
Anthropic's last usable model for cyber was Opus 4.8...Now even in CVP, it cant do shit, and btw CVP on my personal account is rejected again.. I downgraded to $20 plan... @OpenAI's comeback with daybreak and sol for cyber is insane, and massive thanks for the access to individuals.
RT @Ehsan1579: Decades-old C in your kernel, firmware, and compilers, written before anyone imagined today's threats, still trusted by thousands of unaudited dependencies. The chain of dependencies is so deep anything is hackable. Scrape out all the infrastructure and simplify before these models kill a lot of people.
RT @HackingLZ: I thought the first rule of EDR Reversing Club was you don’t talk about EDR Reversing Club.
https://t.co/TR71HmIoZH
@jessi_cata very interesting observation is, most bugs are complex memory corruption vulnerabilities that mostly only sol could pull off running for day(s) with only minimal amount of hand holding from operator once the goal is properly defined
God promised php2shell to wiz 2000 years ago https://t.co/ndeCUyS1uU
AD/Entra 攻击链资料集中成档,便于自查与复现验证。
RT @cr3ghost: If you're into Active Directory, Entra ID or identity security, bookmark this.
Researcher @_dirkjan has built one of the best FREE identity security research archives online.
The rabbit hole covers:
- Active Directory internals
- Kerberos
- NTLM relaying
- Forest trusts + SID filtering
- AD CS
- mitm6 + krbrelayx
- Zerologon
- BloodHound
- Entra ID internals
- Primary Refresh Tokens
- Windows Hello for Business
- Conditional Access bypasses
- OAuth + token abuse
- Cloud Kerberos Trust
- AD -> Entra lateral movement
- Entra -> AD lateral movement
- Temporary Access Pass abuse
- Federated credentials
- Managed Identities
- Intune certificate abuse
- ROADtools + ROADrecon + roadtx
- Actor Tokens
Some absolute classics:
- Relaying Kerberos over DNS
- NTLM relay to AD CS
- Active Directory forest trust bypasses
- Domain Admin from Entra via Cloud Kerberos Trust
- Phishing Primary Refresh Tokens
- Windows Hello key abuse
- Conditional Access bypasses
- Global Admin in every Entra tenant via Actor Tokens
There are also years of FREE conference slides, demos and presentations.
Blog:
https://t.co/8qEBsLuiPy
Talks + slides:
https://t.co/5neZc1JAnQ
Huge credit to @_dirkjan / Dirk-jan Mollema for publishing so much deep identity research openly.
#ActiveDirectory #EntraID #RedTeam
AI 驱动的 N-day 收集正在改写漏洞披露与赏金生态。
HackerScam is telling security researchers to send them php2shell valid POC lol
They just want to collect POCs for their ai
After that they gonna close your report as n/a
Because 100% of the bug bounty programs do not accept new N-day https://t.co/ryBW3iWzsW
自托管多 agent 编排的风险或取决于系统间交互而非单模型。
Watching agents cohabitate is fascinating. This trace in particular reminds me of this paper https://t.co/alsAtq8J4Y
My bet is that understanding the systems agents form together will become a bigger constraint on autonomy alongside humans than individual model capability.
含具体恶意软件家族与投递链,可直接转检测规则。
@fr0s7_ @malwrhunterteam @smica @skocherhan @aaqeel87 We blogged about some of this other malware out of Asia here :)
https://t.co/YC913nWohT
https://t.co/tbazT3uagp
可据此判断涉事 CA 的处置态度与后续吊销范围。
RT @ghidraninja: The response of eMudhra is so full of shit, it needs to be called out. 🧵 https://t.co/8SrxuaEovU
AI 挖洞节奏加快,可据此预排修复与应急窗口。
@jessi_cata i would expect more similar bugs to release in coming weeks/months, its most really attributable to gpt sol broadly being available to defenders unlike anthropic fable with crazy guardrails
多版本变体并存,追溯与查杀的样本线索更具体。
@fr0s7_ @malwrhunterteam @smica @skocherhan @aaqeel87 Yeah, it’s being distributed a lot across Europe and US now. There are several versions floating around and some versions go under the guise of “Winos”, and that was leaked to GitHub in the past.
可作为当日漏洞密度的旁证。
what's with the timing, why are so many vulns dropping at once
硬件自研影响后续固件与基带攻击面。
RT @almamatertech: Meet N1: Apple's wireless chip
https://t.co/Ws63XpSf0a
反映本地模型部署的实践热度。
@Akhnatouch @ForcelineHD shoutout to @BradyTechHobo
as well for educating me, and lots of others in the rea discoard about local LLMs etc
insane setup!
https://t.co/M5LWYayZau
提供漏洞供给周期的横向参照。
RT @fede_k: The abundance of RCE in these days, remind me the 2000. Exploits were shared, traded but also kept private, some lived for years. https://t.co/gjicLCDumY
从玩梗侧面印证该 CA 事件已出圈。
RT @tuckner: Just used LiteLLM to create my first PHP website. The AI even suggested getting a certificate from eMudhra for HTTPS to protect my login page. The future looks really bright 🥳
反映模型挖洞同质化与成本问题。
RT @simplylurking2: POV: frontier labs watching thousands of infosec shops try to re-create the same set of exploits- none of which beat ASLR, but them API bills keep stacking. https://t.co/JCEX0EtYhD
侧面反映逆向与 AI 交叉社区活跃度。
i originally thought people were afking but then I stopped by and realized that was not the case
met some really cool community members like @Akhnatouch @ForcelineHD & had great discussions on creating, reverse engineering and even ai research
可作为技术社区情报源线索。
what i think is really cool is at anytime, you can find a group of people jamming or showcasing their work inside the rea discord https://t.co/MMDFKE9Pl2
提示协调披露机制在实操中的选择性落差。
Chainguard
coordinated release
but only for themselves https://t.co/HKSXCQX3Vm
与当日 CA、模型挖洞事件背景相关的观点交锋。
Are there still any experts who think open source is more secure? 🤔
剩余 WSP 与 PrinterBug 无法中继到 LDAP,强制认证攻击面收窄。
RT @RedTeamPT: 🦛🦛🦛Microsoft patched PetitPotam this October: EFSR now only resolves local paths. This means WebDAV to LDAP Coercion is fixed!
Remaining methods for clients are WSP (coercing SMB) and PrinterBug (coercing RPC), but both cannot be relayed to LDAP 💀💀💀
补丁二进制提前可 diff,攻击者可先于多数用户定位漏洞点。
RT @mikko: "On October 21st at 07:41 UTC, more than six hours before the coordinated release, Chainguard unilaterally broke the embargo and published built images containing the fix. Like other distributors, Chainguard had received the patch in advance so its users could update the moment the vulnerabilities were disclosed. Any attacker could now study the fix in binary form while every other PHP user was still waiting for the release. This disregarded weeks of work by many parties toward a coordinated disclosure."
https://t.co/hszd7sh0NI
可直接封禁的扫描源,显示披露前已有在野试探。
RT @craiu: Currently seeing 196.189.236[.]67 probing for the PHP vuns, suggest to block them on gateways, been hitting honeypots with a bunch of stuff since at least Oct 2.
提供低成本部署侧缓解思路,可对照现有 PHP 运行方式核查。
RT @dcolascione: PHP exploit appears to need ASLR leak. I run my PHP via old-school cgi-bin, one /usr/bin/php process per request, which means no cross-request ASLR info leak.
I guess I'm not vulnerable.
My setup might be the the most secure (if not exactly fastest) way to run PHP.
Do we have php2shell and node2shell on the same day? WTF
https://t.co/jSdegHYCLC https://t.co/6629DXNtIh
RT @otomir23: we used these certs to mitm its config server and enabled adb debugging, this works because they didn't implement remote certificate revocation
Absolute legends! ♥️ Do not believe @wiz_io and their PR stunt. Credit where credit is due. 👏
RT @calif_io: Let’s set the record straight: @lcfr_hax was the first to discover php2shell and develop a working exploit. See his August 5 tweet: https://t.co/I88EQFrUHa
His work convinced the PHP Foundation to invest in fixing this entire bug class. He then worked around the clock to review, test, and retest the patches.
curious, does user data get continuously fed back into the same model through updated checkpoints, or is it only used to train future generations of models?
is it reasonable to update our estimates of cyber risk downward if we repeatedly see catastrophic vulnerabilities like php2shell, kvmescapes, browser full chains, and compromised tls certificates without catastrophic outcomes?
or is cyber risk heavy-tailed, where a rare event could be unimaginably bad? but it seems that never happened, so shouldn't we still update downward?
RT @IntCyberDigest: ‼️ WhiteDate, the neo-Nazi dating site German Pink Power Ranger hacker "Martha Root" wiped on stage, now forwards to GoebbelSuite, a Google parody built on the AfD leak.
https://t.co/NzPUBFYrFV https://t.co/rhB3NDRXMQ
展示 LLM 参与真实漏洞挖掘并提前协调披露的完整流程案例。
RT @OpenAI: OpenAI models helped researchers—operating as part of our Patch the Planet initiative—discover critical security flaws in PHP, an open-source programming language used to run an estimated 70% of websites.
Over the past two months, we led a coalition of maintainers, researchers, and security providers to prepare fixes and protections ahead of disclosure. This duration was necessary because the fix was quite intricate and required a major change to the PHP engine. Every site using PHP can now safely upgrade their version to stay secure, in addition to applying mitigations from various security vendors.
Due to the severity of these flaws and PHP’s widespread use, we consider this bug to be one of the most impactful vulnerabilities in recent memory. It also marks a new phase, where AI can find security bugs with internet-scale impact.
This is an example of the Defender’s Window in action: to our knowledge, frontier AI was able to find this vulnerability ahead of attackers, giving defenders time to prepare.
https://t.co/TW3jrSbB3f
提示即使自身不跑 PHP,共享宿主的邻居被攻破也可能牵连。
RT @PaulosYibelo: there's a real risk that a single PHP server will be exploited to infiltrate a guest OS somewhere, & from there, CVE-2026-99999 could be exploited to breach the host OS, leading to all other guest servers. So even if you don't run php, if some random customer of your host does, you are still going to be affected. This is esp concerning knowing most vps/compute providers still aren't patched.
CA 层级失陷会影响大量下游证书信任判断,需核查信任链配置。
eMudhra Intermediate CA Compromise - @Dennis__Jackson
https://t.co/NXNBo0jf5h
malware-research — Code written as part of our various malware investigations https://t.co/Rj4pmd8iPZ https://t.co/6De58cHQOm
RT @uglybyte: @PaulosYibelo you and @lcfr_hax just blessed all the skiddies in the world with nation state capabilities this week
great job @lcfr_hax & @calif_io for discovering and reporting php2shell
RT @internetarchive: https://t.co/DlpBfnRxqP is currently offline. We are working to restore service now.
规则以开源文件形式给出,便于移植进自有 EDR 或 SIEM。
Rules it maps to:
• Payload Execution by Web Server: https://t.co/KEYOuntUqu
• Payload Downloaded via Curl or Wget by Web Server: https://t.co/kJq3QqwGXf
• Suspicious Command Execution via Web Server: https://t.co/SWmo1iTOqv
• Unusual Command Execution via Web Server: https://t.co/hojx0VYqMb
• File Creation via Web Server (+ polyglot / double-extension): https://t.co/s1ZJgS5b5w
wp2shell walkthrough: https://t.co/T4ulNVyQoP
亲历者视角交代根因与披露过程,比二手转述更可信。
https://t.co/HYxWRPwW1P
披露影响面评估与厂商协同打补丁的经过,可判断严重度。
RT @itszn13: php2shell is the most consequential vulnerability I have ever helped discover. I am proud of how our team worked closely in coordination with the PHP Foundation to provide support and to harden the patch in preparation for this release.
Please read more about our approach: https://t.co/dBlfRky7IL
侧面反映 LLM 辅助漏洞挖掘正在改变研究产出节奏。
Crazy coincidence that all these great vuln researchers had breakthroughs in the weeks right after gpt-5.6-sol was released :D
AI 参与漏洞挖掘让从披露到利用的窗口进一步压缩。
watch the php2shell space, new claude model army is going after it!
家用 IoT 固件的真实利用手法,可迁移到同类设备测试。
Exploitation of TP-LINK TAPO security cameras
https://t.co/TRf5uoEEBq
#infosec https://t.co/ylnHs8AVV3
用户态隐藏手法与检测盲区的对照说明,攻防两端都用得上。
Hiding a DLL from the PEB Loader List (And Why Process Explorer Still Sees It) https://t.co/uVNtBqLufC
RT @lcfr_hax: d935be023a55b04681eccd1d2b8385b4b295e141a5df108e5e979d8d5d7124ac
@S1r1u5_ It's @lcfr_hax; he was the first to find it.
Not Today Satan! https://t.co/aJmdKa9mug
RT @i0n1c: Apparently I am now a Pokémon
https://t.co/rdUtOrL5Vs https://t.co/2iTaBCXjVD
RT @justdionysus: Fancy human generated comics, a good story, and an annoyingly pervasive root cause. Yes, it’s exploitable. Yes, it’s exploitable under ASLR. Yes, disclosure was eventful. @lcfr_hax hacked the planet and then tried to patch it
i am confused. is it wiz, or calif who found the bug?
https://t.co/pEDxxhy1KP
利用已开始绕过缓解措施,说明仅靠 ASLR 与配置加固不足恃。
RT @Dinosn: An ASLR bypass, not click and run but good idea to start on https://t.co/CkpW0OOY4W
补丁本身已成为漏洞研究上下文,旧补丁的防护假设需重新验证。
RT @orenyomtov: The rate of patch bypasses has skyrocketed (8x) this year. 🚀
The good news is that the timing of the increase happens to correlate with Anthropic and OpenAI's security product releases so the increase might be defender-lead.
The bad news are that vulnerabilities that have been reported to be exploited in the wild were bypassed 4x more often, so attackers definitely also got the memo that security patches are highly valuable context for vulnerability research.
For defenders, it's getting important to spend considerable resources on robust and comprehensive patching to stay a step ahead of the attackers.
More stats, like in which linux kernel areas 10%(!) of vulns are directly caused by patches of other vulns, are available in the full report below
对 LLM 自动挖洞能力的现实校准,避免高估本地模型产出。
there's still a considerable gap between open and frontier models, and an even bigger gap between frontier models alone and frontier models in the hands of skilled researchers.
a huge number of people threw tokens at the bug and produced mostly slop PoCs.
the benchmark saturation you see online often doesn't translate into frontier level offensive capability. sure, deepseek flash and kimi k3 can probably develop exploits for a good number of vulnerabilities, but the capability gap is still substantial. they mostly failed for this php bug. prove me wrong.
having a more capable model than your adversary is an advantage, and pairing it with a skilled researcher can make that advantage even greater for defenders. everyone involved in this research had access to the best cyber models.
i personally think we should preserve that capability gap rather than dismiss its defensive value without evidence.
补丁落地前的临时缓解配置,仅覆盖部分漏洞,不能单独依赖。
RT @Kostastsale: A moron has released a POC early for php2shell so here is what you need to do:
If you’re on version prior to 8.2:
Edit php.ini: session.upload_progress.enabled = Off
Then reload php-fpm and restart apache
If you’re on later version:
Update (it’ll be available in a few hours)
In any case, the mitigation for the php.ini should work either way. Not sure if it’ll cover both vulns though so keep an eye on that. I’ll be reporting on follow up activity on windows as a target.
Good luck!
运行时同属暴露面,PHP 之外还需同步升级 Node 各 LTS 线。
RT @itsMikeKipruto: Not just PHP. Node.js has also announced security releases for October 21, with HIGH-severity vulnerabilities affecting its 26.x, 24.x and 22.x release lines.
If you run either stack in production, keep an eye on official advisories and apply patches promptly.
Security maintenance doesn't stop at your application code. Your runtime matters too.
Node.js advisory: https://t.co/rmgw4sOnqU
快速摸清资产中 PHP 版本分布,决定补丁与下线顺序。
RT @cyb3rops: PHP
Patch, take it offline, or put it behind a WAF and hope it filters the exploit requests. I wouldn’t count on a configuration-only fix unless one is confirmed.
For inventory, this Nmap command can reveal PHP versions exposed in HTTP headers:
nmap -sT -sV --version-light -T4 --max-retries 1 --open -p 80,81,443,8000-8010,8080-8090,8181,8443,8880,8888,9000,9001,9080,9090,9443 --script http-headers --script-timeout 10s --script-args 'http-headers.path=/index.php,http-headers.useget=true' <target>
Only scan systems you’re authorized to test. This finds advertised versions, not every PHP server, and doesn’t confirm vulnerability.
RT @sagitz_: Kudos to @ThePHPF for fixing the issue, and to @OpenAI @itszn13 @calif_io @lcfr_hax for the collaborative work on patch validation and disclosure 👏🙏
PHP just released patches. Upgrade asap
RT @halvarflake: Attack surface reduction is the one thing that reliably works.
If your threat model relies on everyone playing by the rules, you're already fucked 🤦♂️
Of course some rando's were going to release the PHP exploit.. it happened every time pre-LLM, so obv it's going to happen now!
Stop acting shocked and get to work h4xx0rs! https://t.co/CjcsQ3MNZR
not that it should be preached, but...
security hygiene > the semi-annual CVE apocalypse
RT @attrc: Full details of a remotely exploitable vulnerability in the core engine of *all* PHP versions will be released tomorrow, October 21st. If your organization has internet facing PHP applications then you need to be ready to patch the minute the update is released or *strongly* consider taking the application offline until you can:
https://t.co/hpdTOdvSsQ
RT @craiu: There’s no shame in taking a website offline while waiting for PHP security patches. https://t.co/5pjr8wZI3m
AI 辅助研究得出的漏洞结论若不经独立验证,会引发全网误报。
Last night's slopfest surrounding the bogus PHP exploit and the subsequent panic wave is a perfect example of why good cybersecurity researchers are still needed, why LLMs are not infallible, and why critical thinking cannot be automated away.
AI can accelerate research, but clanker confidence is not evidence and consensus built on unverified claims in the end is still just speculation.
Next time we might not be so fortunate, so maybe as a community we need to tighten and review how we handle patching and assume leaks will happen and be prepared to counter that.
国家级机构已作响应,PHP 资产清点与补丁窗口需提前安排。
RT @ollieatnowhere: At the @NCSC we are asking all UK organisations and their supply chains across product and services to understand their use of PHP and prepare to patch...
https://t.co/UPT31kqBL6
公开 PoC 多为半成品,短期难形成现成武器化利用。
RT @HackingLZ: So many php2shell repos with pocs and no shells
提供被滥用 agent 框架的清单与一手信息来源,可追溯细节。
RT @NobMiwa: ARTEXばかりが騒がれていますが、悪用されたAIエージェントは他にもあります https://t.co/g7hXxx00JE
Google already had it internally a year ago.
Nvidia says it'll need a lot of compute
M$: it will be in the next Azure release
RT @marckohlbrugge: if this PHP vulnerability allows remote code execution, doesn't that mean we can use the vulnerability to auto-patch all vulnerable servers?
Someone’s gonna use this PHP vulnerability to pwn .union dark web forums.
They all use PHP 😅
RT @slave_2_liberty: Enjoy your daily AI Slop https://t.co/DZfbUIYbUN
RT @bl4sty: had some time to kill en route to #TheSAS2026 dinner party.. so clanked on php apocalypse PoC.. ;-PPpppPp https://t.co/7zWmfC3T9X
Excited to be in the era of "NO RCE" means exploit confirmed
My favorite is when Grok and I are saying the same thing, but Grok is convinced there’s some key nuanced difference that we should consider when there isn’t really in the scope of the conversation.
php2shell is real
RT @i0n1c: A certain AI model seems to be spending 90% of the time fixing and improving its own research harness and only working on the goal 10% of the time. The amount of work that could be done if those numbers were switched…
指纹伪装与 LLM 工具链结合,账号接管门槛进一步降低
RT @_CPResearch_: Our latest research exposes how AntiDetect browsers enable fraud, account takeovers, and coordinated influence operations at huge scale.
Knowledge bases, 24/7 support and MCP servers for LLM integration, the ecosystem is evolving fast.
Read more -->
https://t.co/g4vHtqwKx8
macOS 罕见变形样本,哈希与签名检测手段会失效
RT @objective_see: It’s not every day we encounter metamorphic ransomware targeting macOS! 👀
Our @patrickwardle recently presented at @macsysadmin & @virusbtn on “Heartbreaker,” a new ransomware sample that rewrites & recompiles itself every time it runs!
Blog & slides: https://t.co/ghYQTrAXFL
完整后渗透链路可提炼检测规则,反射加载器手法有参考价值
Symantec's Threat Hunter Team uncovered what followed Hookedge delivery at a NATO naval shipbuilder: NTML theft, a persistent reverse SSH tunnel, and a new reflective loader. https://t.co/b3Dj7aQpcW https://t.co/o538qjbx7z
暴露攻击面板是资产自查与威胁狩猎的可用线索
NorForge researcher Snorre Fagerland analysed more than 20 exposed Cairn panels. One Chinese-language cluster ran over 1,100 attack projects; he also confirmed a live webshell. https://t.co/3Dtw7fcMXR https://t.co/ojn30bM1IS
披露了从 VTL0 内核写绕过凭据保护的潜在研究路径
Credential Guard has a shutdown mechanism inside LsaIso.exe. Signaling it causes the trustlet to gracefully unregister its Kerberos and CredMan RPC interfaces
Currently researching: can a process with kernel write in VTL0 patch the object’s DACL and signal it from usermode?
brave-browser v1.100.20 — Brave browser for Android, iOS, Linux, macOS, Windows. https://t.co/Zk4fvNembK https://t.co/tpd1MQFatE
RT @doomsxroll: @ipurple @_JohnHammond 100% agree. Skilled humans with domain specific knowledge still need to ask the right questions, and evaluate answers - AI is an agent not an actor and cant generate its own intent or motivation. AI isnt replacing anyone with domain specific knowledge. Learning is still valuable.
RT @filescan_itsec: New Filescan research: #JULIUS starts with an obfuscated BAT and ends in a custom in-memory loader and a Go validation payload.
The chain suggests a loader/crypter framework still being tested.
Full analysis:
https://t.co/gVzbPNFQN4 https://t.co/jo3P1jDzyL
RT @GabrielGonzalez: Reverse Engineering Mask ROM
Progressing a bit more on the #Silicon #RE side, I came across the structure used for manufacturing ROM (from the same paper as last time)...
🔗 https://t.co/JGC6UjRV6Z
#HardwareSecurity #Infosec
The real problem is there’s very little chance that it provides $1,000 in increased value to customers. The PS5 jailbreaks have given console insight into exactly the kind of features that customers care about the most. Unfortunately those are the same features that console has been moving away from for years now.
RT @ornith_: Aloha!🌺 Meet Ornith-1.5-122B: No Tradeoff Between Strong and Fast
Stronger. Faster. Leaner. Ornith-1.5-122B delivers frontier-level capabilities with exceptional inference efficiency. With superior instruction following, stronger task decomposition, and deeper understanding of real-world workflows, it achieves state-of-the-art performance among open-source models of comparable size, while running on a single NVIDIA DGX card!!
Open weights under the MIT license.
Coding
✅SWE-bench Verified: 0.845
✅TB2.1: 0.813
✅CyberGym: 0.800
✅NL2Repo: 0.512
Agentic
✅HLE: 0.446
✅BrowseComp: 0.785
✅MCP-Atlas: 0.746
✅Toolathlon: 0.708
🤗Hugging Face: https://t.co/w1hD6rra1o
We can’t wait to see what you build with Ornith-1.5-122B.
RT @oct0xor: My colleagues Haidar Kabibo (@haider_kabibo) and Sergey Sidorov are presenting on hacking barcodes and warehouses #TheSAS2026 https://t.co/GZmF2kevqR
Yes, sorry, so ...
- the CVSS is "only" 9.2
- they rescheduled from 20th to 21th 14:00 UTC
Results:
https://t.co/ePVCN7kH0j
Company issued workstation https://t.co/4Eb38N8bnU
规则可直接上线做检测,需先建基线以压低误报噪音。
RT @Kostastsale: A possible Sigma rule to detect a future php2shell exploit:
https://t.co/PEJmHtHi8k
Curtesy of @nas_bench
(You might see FPs in your network(s). Baseline first...)
自动化攻击工具跨行业复用,说明其已进入实战部署阶段。
ARTEX seems to be quite popular lately again: https://t.co/e3BHGRMiuN
无需认证即可触发,覆盖多个默认开启的 Windows 服务组件。
RT @oct0xor: Azure Yang (@4zure9) presents on Windows pre-authentication bugs! 19 CVEs in LDAP, MSMQ, iSCSI, OCSP, MSCEP, etc. #TheSAS2026 https://t.co/9UEefZ2cuS
在抢修喧闹中提供反向判断,避免按幻觉 PoC 做错误处置。
i don't think there's a working public exploit. people seem to be just hallucinating with models, the bug is hard to exploit.
also, it's wildly irresponsible to publish anything about the bug before the embargo lifts. even hinting at the technical details is dangerous. please don't do it
商业检测规则可被模型批量还原,影响检测产品与绕过研究。
RT @Kostastsale: I used Opus 5.5 on max and GPT-6 Astra for 5 days straight and I reversed engineered Elastic Security and extracted all the rules. I made them available here:
https://t.co/fGAoNleFEW
You’re welcome.
协作平台流量难以区分,常规网络审查容易放行。
A project that uses Confluence as a C2 🧐
https://t.co/RWLe3at9Av https://t.co/LsCyBuzobT
服务名与可执行路径不匹配是低成本高命中的排查点。
We had a Windows machine where one process kept coming back after every reboot.
At first, it looked like normal Windows activity because the service name was:
WindowsTelemetry
That sounds believable enough.
Windows has plenty of telemetry components, so if you are checking quickly, you might not even stop there.
But I checked the full service configuration.
The executable path was:
C:\Users\kevin\AppData\Roaming\Microsoft\Telemetry\telemetry.exe
That did not make sense.
A service running as LocalSystem should not normally be launching an unsigned executable from a user’s AppData folder.
I checked the file signature.
NotSigned
Then I checked when the service was installed.
Event ID 7045 in the System log showed that WindowsTelemetry had been created the previous night around 11:08 PM.
The service was configured to start automatically and run as LocalSystem.
That meant the binary was not just persistent.
It was running with very high privileges.
I pulled the PID for the service and checked its network activity.
The process had an established HTTPS connection to an external IP address.
At that point, we isolated the machine.
The interesting part for me was how normal the service looked from the name alone.
WindowsTelemetry
Microsoft\Telemetry
telemetry.exe
Everything was named to make you move past it.
But once you looked at the path, signature and service account, the picture changed completely.
This is why when I am reviewing Windows services, I do not only look for strange names.
I check what they actually execute.
I check where the file lives.
I check who signed it.
And I check which account the service runs under.
A malicious service does not need a suspicious name.
Sometimes it just needs a name boring enough that nobody bothers to open the properties.
暴露 AI 生成漏洞利用在真实应急中的信息污染问题。
i think this evening-into-morning has been a fascinating storm of chaos and uncertainty with potential proof of concept exploits (generated by LLMs) being shared publicly and privately (then analyzed by LLMs) without clarity or understanding of what is actually "the" exploit or if it is "other" exploits (found by LLMs) all to hope for potential defenses (built by LLMs)
we used to be so concerned with robots hallucinating
at this point we might be the ones hallucinating ourselves
攻击链与目标清单完整公开,可对照排查同类暴露面。
RT @tuitesteban: No defender caught this Russian-speaking operator. They went after #Ukraine’s state data-exchange system, and the working directory sat open for 17 hours... That is where everything was: the access log that proves execution, the scan output, the full target list
The https://t.co/42EL2mKsZ6 research team rebuilt the whole campaign from it: a solo operator going after a state data-exchange system with a borrowed Log4Shell chain, and we only know its shape because they left the door open!
Here is how we did it 👇
https://t.co/ZYQqsU45Ew
Agent 自恢复能力提升,同时意味着权限边界需要重新评估。
we're going to make rea a lot more robust in the upcoming v6.8 update
ive been reading the posts + watching youtube videos @tonbistudio
there will be a big focus on making it more comfortable for agents to use + adjustable so they can directly recover without human input
it's interesting that eMudhra is a family-run business. not suggesting any relationship between how it's run and its security practices or innovation, but i can't help thinking about @captgouda24 "What's the Matter with India?"
he argues that india's dysfunctional judicial system makes businesses to rely on the oldest form of trust, family, thus limiting innovation and scale.
also very ironic, company building trust infrastructure for the internet (TLS) itself relying on the oldest form of trust, family.
https://t.co/G4LcL6kABc
I found 1021 domains similar to your sharing in the past 30 days😅 @Malwarehunterr https://t.co/xnDOcNOi1H
@_JohnHammond True, but how many companies have actually reduced headcount because of AI? Organizations still need skilled humans with hands-on keyboard experience to investigate threats, apply the right context, and respond appropriately.
RT @encrypted_past: Raw Bus recordings are a little glitchy.
https://t.co/vvdNTp8jJG
OpenEDR 2.5.1.0 💋😼
#OpenEDR
@XcitiumHQ https://t.co/WfTVnZFkVG
Sometimes I have a tendancy of writing functions with too many lines, which causes bugs and prolonged troubleshooting.
So I wrote a tool which becomes like an add-on to gcc and g++, that counts the lines of every function and gcc errors out if any is >20 lines. Pretty cool.
JB
LLM 批量审计已在真实项目上见效,PHP 生态可能迎来漏洞集中爆发。
It’s going to be really funny if everyone pointing their LLMs at the PHP codebase tonight finds dozens of OTHER critical vulnerabilities aside from the ones getting fixed tomorrow
根信任被彻底击穿,中间人攻击门槛降至最低,需核查信任库中的来源。
RT @jakehalloran1: its obviously not *good* but admittedly having a private key of *4* as a globally trusted cert authority is one of the funniest bits of all time
把漏洞利用原语搜索自动化,显著降低二进制利用的准入门槛。
yes, I just explained it. you filter based on the high IL expression that gives you the primitive you’re looking for. a vftable call is usually a this call, and typically you’ll have some control over that object. say you want the object to be freed and the reference count of the object is at +0x18. then the script would search for the expression *(this+0x18) -=1 , which decrements the ref counts to 0.
现成的威胁情报整理工具,可直接用于事件响应中的 IOC 检索。
iocs — Indicators of compromise from to analysis and research by Nextron Threat Research team https://t.co/2NstDA1B4t https://t.co/ZSvemSfes4
苹果平台监控层绕过的具体手法公开,可用于移动端攻击面评估。
RT @oct0xor: Alfie CG (@alfiecg_dev) dissects the SPTM bypass used in Coruna (it also exploits AGX and uses more obscure hardware registers 👀) #TheSAS2026 https://t.co/trxb5kDxq6
内核竞态是本地提权常见入口,讲解含可复用的利用思路。
RT @oct0xor: Alexander Popov (@a13xp0p0v) presents on exploiting a tricky race condition in the Linux kernel. This exploit is beautiful. #TheSAS2026 https://t.co/jx8kNXxTwZ
给出 AI 辅助原语挖掘的实现路径,思路可直接迁移到自有样本分析。
the script iterates each line of the function ripping out the high IL which looks like this. this could correspond to a primitive. sometimes the conditions behind the operation are not achievable, but restricting to functions that are small + the AI can usually reason ab reachability
恶意 Go 样本分析刚需工具,支持导入 IDA 使用。
GoReSym — Parses Go binaries to recover symbols, function metadata, types, file paths, and embedded strings, including stripped or UPX-packed samples, with IDA Pro import support. https://t.co/k27QHzKWzs https://t.co/tsJitFvjGx
RT @HackingLZ: I thought the first rule of EDR Reversing Club was you don’t talk about EDR Reversing Club.
https://t.co/TR71HmIoZH
RT @oct0xor: We just dropped the first episode of our Cyber True Crime podcast, where we discuss Operation Triangulation and Coruna. Check it out! https://t.co/33CbPRbdwS
another xkcd hyperstition becoming reality? this has to be a glitch in the matrix.
httpx://xkcd.com/221/ https://t.co/n6wkAHWogJ
in the script it also has filters for lines of code in the function, parameter count, etc. there are so many valid kCFG functions it’s pretty easy to multiple targets that correspond to workable primitives. the advantage of using AI too is that it is capable of searching for many different potential primitives at a time.
RT @LowLevelTweets: hey man. if you run php.
turn it off.
Personally my bet is on an exploitable stack overflow in the recursive acronym processing code
RT @thsottiaux: Day 16/
You can now cache for 12h in the API and for logged in users across Codex & Work we keep cache forever and you don’t have any penalty for coming back to an old conversation or resuming after a few hours and are now guaranteed to hit the cache.
边界设备固件与密钥外泄,攻击面分析可直接复用。
Decrypted the whole Fortinet 8.0.1, found vulns and encryption keys were dumped from memory, rootfs is also decrypted.
The size is pissing me off, wym its 44 GB.... https://t.co/dOvU5upxYY
不改 AD、不留日志的静默提权路径,BloodHound-CE 已能映射。
RT @g0h4n_0: 📝 New blog post - ESC13: Being a Phantom Member of a Group 👻🔥
Enroll in one cert template, and your certificate injects a group's SID into your Kerberos ticket. You "become" a member without ever being added to the group. No change in AD, no noise.
🦀 RustHound-CE v2.5.26 now maps this path in BloodHound-CE. Huge thanks to @marbasec for the feature and the many bug fixes! 🙏
📝 EN: https://t.co/7TgblR6pah
📝 FR: https://t.co/3lz7fs7oQF
#ADCS #BloodHound #RedTeam #Rust #Pentest
显示 agent 编排已能产出真实可利用漏洞,本地 agent 风险面同步上升。
RT @J4ck3LSyN: @theonejvo It was a mix, I think between us 3 is was grok, glm, nemotron & deepseek
Ran in hermes-agent
@acd421 @Archknight23 did i miss any?
自建证书透明监控成本低,可及时发现仿冒域名与新签发证书。
certstream-server-rust — High-performance Certificate Transparency (CT) monitoring tool written in Rust. Real-time stream of newly issued SSL/TLS certificates from CT logs... https://t.co/Nj0nSO0oir https://t.co/sBBc37gcsz
RT @ordinary_beaver: @C2IRIS You mean it’s already being exploited?
RT @Yaya4_4: @J4ck3LSyN And here we go y’all are posting 0days that could own half the web
RT @Heartbeat54_: @MarkLundeberg @J4ck3LSyN Normally, I would agree, but the disclosure of a vulnerability existing would be enough for bad actors to find it. Someone might as well publish it to force the patch publish
RT @wescopeland_: @J4ck3LSyN coordinated disclosure was in 13 hours. you couldn't wait 13 hours.
RT @DevuanOrg: At Devuan, we're not driven by profit or marketing. We recognize the achievements of other communities through evidence, not hype. That's why we salute @OpenBSD on its 8.0 release: an outstanding community effort putting users' security first.
RT @sysadafterdark: Uh, yeah I’ve seen enough. I’ve been meaning to migrate to flat-file static pages so I guess that just got moved up the priority list.
There was a hint in the last time i tweeted Thanos - he's PHPurple. https://t.co/gynf4bAgud
PoC 细节临近公开,防御窗口很短,需提前排查版本。
@h4x0r_dz https://t.co/fBMCU6gAaK
details soon :<
@lcfr_hax Well done 👏
Fun times ahead!