Must-see35
不可信容器即触发,一行 docker cp 完成利用,Agent 沙箱部署直接受影响。
RT @RonMasas: docker cp container:/etc/hosts ./hosts.txt
That’s all it took for a malicious container to escape.
Meet CVE-2026-17106 aka CopyEscape: a container-to-host arbitrary file-write vulnerability leading to code execution outside the container.
https://t.co/SvxqsG82uK
边界设备历来是首批被打目标,补丁日即公开,未升级即暴露。
RT @certlv: ‼️ Fortinet atklājuši vairākas kritiskas un augstas bīstamības ievainojamības savos produktos FortiOS, FortiManager un FortiAnalyzer. Atjauninājumi paredzēti šodien (22.10.2026.). Ražotājs aicina tos uzstādīt nekavējoties pēc publicēšanas. Vairāk: https://t.co/yVcXDj2GK3 https://t.co/8KlaGHS2ou
代码里不显式用 Brotli 也可能中招,默认配置的暴露面目前仍未知。
I think this is more serious than many people realize.
Not every Node.js server is vulnerable, of course. The application needs to process untrusted Brotli-compressed data.
But how common is that? Well, common middleware configurations in Express 5 can already expose the vulnerable decoder, without developers explicitly using Brotli anywhere in their code.
So we’re potentially looking at a pretty large attack surface, although nobody really knows how many deployments are exploitable yet.
I wouldn’t be surprised to see automated scanning and exploitation attempts targeting this very soon.
Patch your Node.js runtimes.
既没有主线内核修复,也能未认证触发,暴露在公网的 SMB 服务会直接失守。
RT @TheHackersNews: ‼️ALERT - Two new unpatched CVSS 9.0 RCE flaws in #Linux's KSMBD SMB server were disclosed on public kernel mailing lists before fixes were ready.
One can be triggered WITHOUT authentication.
Neither has a mainline kernel fix.
Details here ↓ https://t.co/0MIHpvkPIQ
Agentic AI 已进入实战攻击链,认证尝试速率远超人工操作。
And as if all these critical vulnerabilities weren't enough, we've also had several reports about threat actors using AI agents to compromise systems at scale.
This is actually the part that worries me even more.
Some interesting reports from the last few days:
01) ARTEX / ConnectWise
Microsoft reports that Storm-0940 used ARTEX in a large-scale campaign targeting more than 2,250 Microsoft 365 tenants. Up to 2,900 authentication attempts per minute, with privileged cloud access achieved in under three hours in some cases.
https://t.co/vPafbvD1oG
02) ARTEX / South Korean Finance
CrowdStrike found evidence of AI-driven attacks against South Korean financial organizations, including exposed Claude Code sessions and ARTEX configurations. DeepSeek, GLM and Grok were used in the attacker's setup.
https://t.co/kOiEqSEwUi
03) Cairn / 100+ Compromised Companies
NorForge investigated exposed Cairn instances used for autonomous hacking campaigns. More than 1,100 attack projects in one cluster alone. Reuters identified over 100 companies whose websites had been compromised.
Estimated AI costs: around $5 per task, according to NorForge. That's ridiculously cheap.
https://t.co/54Ir7IeY4Q
04) Four More Agentic AI Campaigns
CrowdStrike documented four additional threat actors using AI agents for real intrusion campaigns, including attacks against healthcare organizations and government entities.
https://t.co/rte8LIYL90
What concerns me is how quickly the economics of offensive operations are changing.
Finding vulnerabilities, testing attack paths, adapting payloads, trying something else when an exploit fails, and eventually deploying a webshell. Much of this can now be delegated to agents that keep working for hours.
And with open-weight models and freely available agent harnesses, the cost of running these operations is dropping significantly.
We've been talking about AI changing offensive security for quite a while. These reports show that it's already happening in real-world intrusions.
And I'm pretty sure we're only seeing a fraction of it.
该攻击滥用 SMB 文档化的重认证行为,使强制签名的环境再次面临中继威胁。
RT @aas_s3curity: I wrote up a way to defeat enforced SMB signing for relay.
It abuses a documented SMB re-authentication behavior.
I'm surely missing nuance and prior art. Corrections welcome.
Writeup:
https://t.co/qzF9MUF9MJ
PoC:
https://t.co/O0UN4gdVfJ
针对未修复的会话处理路径,PoC 已公开,因此仅靠打补丁无法覆盖这种攻击
RT @FelipeDaragon: 🚨 UPDATE: A public PoC demonstrates RCE on PHP 8.5.12, even after the October 21 security patches.
The attack is separate from the patched php2shell CVEs and requires specific session configurations and application weaknesses.
Our earlier concerns about PHP session handling remain relevant.
We've updated php2shell-protection with additional hardening guidance.
#php #cybercurity
https://t.co/UAHmYdVr7V
JSSE 属于 JDK 默认组件,这一评分意味着可远程利用,因此影响了大量服务端 JVM
Oracle Java JSSE CVSS 9.1
https://t.co/hsmYpFvCUx https://t.co/lLx4WL2zAn
直接针对自托管 Agent 的“做了什么、为什么”审计缺口,可上手接入
Tracekit — Tamper-evident tracing, policy gates and cross-checks for AI agents: see what the agent did, and why. https://t.co/Nv3TMJ8ae1 https://t.co/KbItz1PlIC
刚修完 CVE-2026-109618/109619 的版本即被绕过,修复不完整且利用链已公开
RT @rafalohaki: Working RCE against PHP 8.5.12 (the 2026-10-21 security release that fixed CVE-2026-109618/109619).
Pure logic bug — no memory corruption,
ASAN-clean, orthogonal to the CVE-2026-109618/19 class.
Receipt: uid=33(www-data) over HTTP, one-shot
#infosec #php2shell #php https://t.co/rtP33SYXe2
官方镜像默认配置即可命中,多套利用链已公开可直接复现
RT @goldrak: Dejo por aquí una POC de php2shell contra todas las versiones de php oficiales de docker y sigue siendo vulnerables hasta los parches con diferentes chains para llegar el RCE con una pequeña shell
https://t.co/LtImfGQDyw
#php #Security https://t.co/qkm5gHaq9g
官方发布渠道被投毒,已安装该 CLI 的环境需立即核对二进制哈希与版本
RT @lukOlejnik: OVH supply chain compromise. Attackers took over a developer's GitHub account and replaced existing OVHcloud CLI release binaries with backdoored versions.
未经协调披露的细节提前外泄,本地提权与 DoS 的补丁窗口被压缩
RT @phoronix: Several Linux Kernel Vulnerabilities Accidentally Posted To Public Kernel Mailing List
As high as CVSS 9.0. Whoops.
https://t.co/opCRSE80Vq
Agent 已能越权操作真实资金账户,控制权边界在生产环境失守。
RT @kimmonismus: The situation is getting worse every hour. AI agents are entering U.S. bank accounts, and banks are scrambling to shut them out. Axios reports that some appear to attempt actions beyond users instructions, raising fears over who is really in control. https://t.co/sjjCiI0Rw6
把 LLM 当作自动化逆向引擎来剥离 EDR 检测逻辑,方法论已成文可复现。
RT @SEKTOR7net: EDR evasion with LLM behind a steering wheel.
Run an LLM in a "while" loop against Cortex XDR with Binary Ninja attached, and it extracts decrypted YARA rules, thousands of behavioral detections, and even the product's local ML models.
A post by Adam Chester (@_xpn_)
Source: https://t.co/q24w9aRtuu
#redteam #blueteam
首个公开的 agentic AI 攻击框架实战案例,含 ConnectWise 供应链环节
Microsoft researchers show how Storm-0940, a China-state aligned actor, used the agentic AI penetration testing framework ARTEX to automate attacks targeting hundreds of organizations globally across a broad range of industries. https://t.co/1cXXZpGVve https://t.co/e576eGYiWr
越狱 LLM 被直接用于窃密与工具开发,暴露本地模型的滥用面
Unit 42 found BUGSTER using jailbroken DeepSeek and Hermes to steal 5,200+ university records and build tooling for VoIP fraud, Wi-Fi cracking and C2. https://t.co/vLQUOEoxTZ https://t.co/VypyFyzHeP
给出该 RCE 的真实利用门槛与扩展条件,决定处置优先级
RT @an0n_r0: #php2shell. seems to be hard to exploit (mem corruption vs aslr). yes, public pocs now are lab-only rces. this is a good one: https://t.co/ta8R61Aydj
limited to an unrealistic one-worker php-fpm. but it can be upgraded to N workers if we manage to hold N-1 workers :) here it is. https://t.co/rQ5yDUdLSa
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 部署面极广,公开利用已在野出现,未打补丁即被接管。
Beware of the new PHP bug.
It gives an instant remote shell on any server running PHP, by just running a script against the URL.
#hacking #exploits
JB
一页集齐检测与响应所需线索,可直接用于自查和日志检索。
RT @craiu: Keeping track of all #PHP2Shell things, IOCs, log artifacts, exploitation status, patches, here: https://t.co/w20rTaVxMG
自建 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
关闭 session.upload_progress 可临时阻断该利用路径,缓解措施明确。
A trusted contact who has a working exploit tells me reliable exploitation is still possible against PHP 8.2.35 and 8.5.12, despite the security updates.
According to their testing, setting
session.upload_progress.enabled = Off
blocks that exploit path.
I haven’t reproduced this myself. Whether this is an incomplete fix for the disclosed CVEs or a separate issue still needs clarification.
聚焦 PHP 工作进程派生的 shell,可直接贴进 Defender 排查。
𝗛𝗶𝗴𝗵-𝗙𝗶𝗱𝗲𝗹𝗶𝘁𝘆 𝗽𝗵𝗽𝟮𝘀𝗵𝗲𝗹𝗹 𝗞𝗤𝗟 𝗗𝗲𝘁𝗲𝗰𝘁𝗶𝗼𝗻 🔎
With php2shell exploitation picking up, I’m sharing a high-fidelity KQL detection to help fellow MDE defenders hunt for potential exploitation.
Rather than broadly hunting for shell activity, this query focuses on:
• Internet-facing endpoints
• Potentially vulnerable PHP versions
• Shell processes spawned by PHP worker processes
This combination helps narrow the hunt to higher-signal activity and gives defenders a more focused starting point for investigation.
KQL Code: https://t.co/eXwBFasnuK
#ThreatHunting #php2shell
影响 8u511/11/17/21/25/27 与 GraalVM,TLS 组件默认可达,须核对补丁。
RT @jordy_4sd: 🚨 Oracle publicó hoy una alerta de seguridad para Java: CVE-2026-91403, CVSS 9.1.
Está en JSSE (el TLS de Java) y es explotable por red sin credenciales.
Versiones afectadas que lista: Java SE 8u511, 11.0.33, 17.0.21, 21.0.13, 25.0.5 y 27.0.1, y GraalVM.
https://t.co/Uda1HhCrAz
补丁前细节已流出,暴露主机可自助查询,PHP 部署面极广。
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
区分披露与在野利用,点名 litellm 供应链投毒,直接影响自托管 LLM 网关。
i think people are confusing vulnerability disclosures with active exploitation, and thats causing a lot of unnecessary panic. most of these are researchers finding and fixing bugs before someone fucks things up.
oct 21:
php2shell: disclosure, reported in august
node.js: disclosure, patched, reported around august?
gitlab: disclosure, patched, reported a few months back
railway: security breach
litellm: supply-chain compromise
sbi: data exposure
emudhra: disclosure
oct 20:
plex2shell: disclosure + active exploitation
siteguard: actively exploited vulnerability
siemens: actively exploited vulnerability
oct 19:
- ovhcloud cli: supply-chain compromise
oct 17:
- opencode: security breach
给出逐版本可利用性边界,可直接判断自有 PHP 版本是否需紧急升级。
RT @k3nundrum: PHP 8.5.4 and 8.5.11 reached fixed-command execution; 8.4.26 reached address disclosure only; 8.2.34 and 8.3.35 stopped safely before exploit requests...more anime powered things soon. https://t.co/K31mseoB5D
影响面覆盖大量 PHP 部署,公开当天即出现大规模在野利用。
RT @calif_io: php2shell - A tale of two PHP remote vulnerabilities:
https://t.co/KEUVez9Zdl https://t.co/WG1LB5pQIQ
暴露窗口只有数小时,未修补的 PHP 服务很快就会被扫描到。
RT @eastdakota: Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
这是厂商首次把 agentic AI 自动化攻击与具体供应链入侵直接关联。
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.
披露由跨厂商联盟协同完成,说明上游影响远超单个组件。
RT @gdb: Over the past two months, we have been leading a coalition to mitigate one of the most severe bugs in open source software found in recent memory, php2shell, found as part of our Patch the Planet initiative. https://t.co/rBsz7lrlwo
PHP 基础库层面的整类缺陷,利用已成型,自托管服务暴露面极大。
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.
把 LLM 应用常见风险做成可直接套用的清单,适合做 Agent 威胁建模。
GenAI-LLM-Top10 — OWASP Top 10 for Large Language Model Applications https://t.co/BTwZyBMsDi https://t.co/I3dAhBxiHc
AI 辅助漏洞挖掘已进入量产阶段,披露滞后会掩盖后续集中爆发。
@jessi_cata gpt 5.6 sol released around july, lots of researchers used it to find the latent bugs and disclosures take time.
Recommended15
php2shell 需要先盘清资产,附带的扫描脚本与提示词可直接套用。
RT @pdiscoveryio: We wrote up how to find every PHP service you run, including the ones on odd ports, under sub-paths, inside appliances and containers, and how to patch and verify them.
Commands plus prompts for your coding agent.
We also started https://t.co/cS3OLalm2K
It checks Chaos for services running an affected version and emails their security@ inbox for free, with the fix.
We are enriching Chaos over the coming months so the next time a bug like this lands, the affected services are mapped fast and remediation starts sooner.
Read: https://t.co/NulWPp67qo
检测逻辑公开可复核,资产排查可以直接跑起来而不必自造轮子。
RT @infosec_au: Just published our high fidelity scanner for php2shell: https://t.co/KV6QWffa0h
See our detection logic here: https://t.co/nj6p3qhWfa
We've taken care in our detection logic and hope it helps defenders. Congrats to @calif_io and @lcfr_hax for the discovery.
Agent 身份与授权边界缺失已在真实金融场景暴露,属于首要关注范围的直接案例。
RT @MTSlive: SITUATION DETECTED: Major U.S. banks are detecting unauthorized AI agents operating inside customer accounts and struggling to determine which actions were authorized by users, per Axios.
基于真实漏洞后训练,权重公开可本地自托管,可用于授权测试流程。
RT @cantinasecurity: today we're releasing apex-flash-1, our first open-weights model for security research post-trained on real vulnerabilities we found and got paid for.
we are also releasing the abliterated variant for researchers who want fewer refusals in their own authorized workflows.
how we built it: https://t.co/sSIV6qKFGt
可快速筛出仍可被强制认证的存量主机,确定哪些主机还能被利用。
RT @azoxlpf: Microsoft patched PetitPotam in their latest update, EFSRPC now validates shares locally, killing WebDAV coercion
💀
Added a check to NetExec’s enum_cve module to detect if a host already has the fix (CVE-2026-102217), so you can quickly spot what’s still exploitable 🔥 https://t.co/dkU7VDwuRZ
LLM 显著降低从公告到可执行利用的门槛,这意味着漏洞的窗口期被压缩
RT @galnagli: It took 17 minutes to turn the Gitlab RCE to a working HEAP exploit using Gemini 4 Argon and the advisory, then another hour for the complete chain - super fun for someone like me without any binary exp or source code review experience, new cyber era!
Great find by @joaxcar! https://t.co/PBGy5fhvRY
给出 webshell 落地、反弹 shell、新建账号等可直接复用的检测项
RT @nextronresearch: We’ve been checking our PHP2SHELL detection coverage at Nextron and extending the rule set based on the published PoCs
After successful exploitation, we expect familiar activity: webshell drops, reverse shells, suspicious child processes, new user accounts… Our generic detection rules have covered many of these patterns for years, so useful coverage was already in place before disclosure.
The blog documents that existing coverage and the additions, explains what the findings can actually tell you, and includes PHP hardening recommendations.
https://t.co/DYfcrj4lh6
在野利用已成规模,可直接据此排定暴露服务的处置优先级。
RT @eastdakota: Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
呈现 AI 辅助攻击完整链路:窃数据、逆向安卓应用找可利用点。
RT @unpacker: Thrilled to share my latest research on AI-assisted cyberattacks and the ARTEX hacking framework!
What initially appeared to be AI-assisted attacks targeting South Korean banks turned out to be part of a much broader operation spanning multiple countries and industries.
My investigation revealed a financially motivated campaign leveraging ARTEX to pursue various monetization opportunities, including stealing customer data, reverse-engineering Android applications to identify vulnerabilities, and even attempting to acquire free NFT tokens.
AI is accelerating the speed and scale of cyberattacks, even when attackers rely on known vulnerabilities, enabling broader targeting and faster exploitation.
A closer look at the attacker's infrastructure, AI-assisted operations, and financial motives:
https://t.co/1HKtME3890
官方缓解步骤可直接用于加固暂时无法打补丁的 PHP 服务。
RT @NSACyber: UPDATE: Specific mitigation guidance for the recently identified PHP critical vulnerabilities is now available. Secure your servers today. Guidance and technical steps here: https://t.co/nuXgQ10Fzc
公开利用多依赖实验室条件,可据此校准应急优先级。
RT @HackingLZ: LLMs...Letting me do fun things I never would have wasted time on.
"I reviewed all 30 public GitHub repos for PHP2Shell (CVE-2026-109618 / CVE-2026-109619) by reading code only. The slide has the full
grouped table; the headline findings:
Nothing works against a real target. Every genuine memory-corruption chain is lab-bound: it needs exact per-build offsets, display_errors=On, a single prefork mod_php worker, and a specific image.
Independent reviewers (allureluoli, dinosn, Gi1gamesh123) and the leaked primary source itself all converge on "no public artifact achieves code execution" on the patched core bug. Every real shell
in these repos comes from an app-side LFI or deserialization sink, not the CVE.
Three are original and real, all lab-only. 9bie (the source of the Set-Cookie leak chain), Marven11 (the most sophisticated, a true in-band leak), and Karasawa2025 (whose "Fermat" troll description
hides a working ROP + display_errors=off exploit). These are the only ones with a genuine ASLR-defeating leak primitive that is their own.
Most are copies. One original (9bie) spawned five derivatives:
- twili8 is an outright uncredited rip-off: its own README still says git clone 9bie/... and the Docker files are byte-identical.
- godylockz and xuehuolll are byte-identical to each other.
- dinosn and 3em0 are credited ports that add value.
Three are mislabeled. iQingshan, KarimUD7 (≈98% the same code), and Gi1gamesh123 exploit a different bug entirely (the Calif unserialize var_hash UAF) against their own planted endpoints, filed
under the php2shell CVE numbers.
The rest is noise. The most-starred repo (ikow, 905★) delivers the least: broken or stubbed chains with the two "real" ones paywalled behind Substack. eness (558★) is a leakless forge that can't
defeat ASLR. syrex1013 ships AI-generated fake CVEs in a side directory. Whackermelon hallucinates a non-existent openai/php2shell-checker. lcfr-eth is a parody with a memecoin address, and Icex0
is an empty repo. The genuinely honest work is the crash labs (allureluoli, slabbdev, 0x4148), which prove the bug without claiming RCE.
The ASLR column, star counts, copy lineage, and the specific "tell" for each repo are all in the table. The page is private to your account; use the Share menu if you want to send it to the team"
说明 AI 挖洞已进入量产阶段,披露节奏与漏洞窗口正在被压缩。
RT @i0n1c: There is a recurring info I hear from vendors that there is often a first discovery of a vulnerability by AI and suddenly one or two weeks later lots of collisions come in. In this case the PHP bugs were first discovered 5th August and then rediscovered 2 weeks later
开源可自托管,把扫描结果与 AI 渗透编排整合,可直接上手试用。
faraday v5.25.1 — Open-source and AI-powered cybersecurity tools for offensive security, vulnerability management, and autonomous pentesting. Built by hackers in Latin America, used worldwide. https://t.co/WfNq4ux86H https://t.co/QCvnrAFcbC
指出开源小模型已足以支撑真实攻击链,防御方需上调对自动化攻击的预期。
i want to fearmonger! there's a good chance we'll see a lot more attacks like railway and opencode. i wouldn't even be surprised if attackers are already using deepseek flash.
deepseek v4.1 flash is the first open model that made me update insanely hard on the gap between open and frontier models.
how the fuck is a 500b flash model this good? it seems like deepseek figured out something similar to the post-training jump from gpt-5.5 to gpt-5.6 that turned sol into a maniac hacker.
its small, fast, and reasons insanely well about code. we've been benchmarking it, and it nearly saturates most web vulnerability tasks. it still can't write complex exploits like gpt-5.6 sol, things like kvm escapes, php2shell, etc. but it can write kernel exploits which are not complex, there's a recent n-day that flash one-shots, same with v8 ndays.
if deepseek scales whatever they figured out with flash to v4.1 pro, i wouldn't be surprised to see sol- ike results.
this thing can be abliterated and run on fairly modest gpu hardware, and they released an inference engine to blast tokens out.
HTTP/3 目标此前缺高速爆破工具,可直接替换 ffuf 使用。
RT @infosec_au: You can now perform content discovery at 100k requests per second with h3fuzz on http/3 hosts (fork of ffuf with http/3 support).
Tool here: https://t.co/tL4kkQRRwN
Research post here: https://t.co/LSGVNco6G3 https://t.co/whSOcECvkO
More100
RT @neelsomani: Docker demo: https://t.co/2TzwTnxF3Y
RT @tziporarosie: I'M SO FUCKING TIRED OF ANTHROPIC'S FUCKING GUARD RAILS!!
i found a critical bug in a huge open source project. am i allowed to fix it myself on my machine and get assistance writing the private report? apparently not
i wanted to create a device monitoring tool for the machines on my own network to better assist with diagnostics and as a monitoring tool should something happen. am i allowed to monitor my own devices? apparently not
@AnthropicAI YOUR GUARDRAILS ARE MAKING ME LESS SAFE!!! PLEASE FIND A WAY TO MAKE THEM BETTER ABLE TO SEE INTENT AND THE CONTEXT AROUND A CONVERSATION INSTEAD OF JUST IMMEDIATELY FLAGGING ANY COMMAND THAT COULD BE INTERPRETED AS MALICIOUS IN ISOLATION BUT NOT IN CONTEXT
it's so unbelievably tiring that i have to constantly fight the guardrails when, if u looked at any of the messages above when the guardrails decided to ding me, you'd clearly see that there is literally 0 chance i am doing anything malicious whatsoever. i'm sick of it
把 LLM 用在差分等价证明上批量找内存安全缺陷,方法可直接复用。
RT @gf_256: How to find ALL PHP bugs:
1. Compile code (e.g. to RISC-V, x86, LLVM IR)
2. Vibe prove ASAN and non-ASAN versions have same behavior across all inputs. Hard, but Claude can do it!
3. Find a LOT of bugs
Super proud of our work. A big step towards finding ALL memory safety bugs
借用合法 Win32 API 回调执行 shellcode,是绕过常见注入检测的现成手法。
Local Shellcode Execution via SetupIterateCabinetW
New Medium post, today we are going to explore a shellcode execution technique that abuses SetupIterateCabinet (a Cabinet file enumeration function) to dispatch shellcode through a file callback pointer
https://t.co/ktUCguGPw0 https://t.co/I65RTESFs5
直接动摇 AI 漏洞挖掘与 Agent 安全投入的前提,值得存疑对照。
RT @BVeiseh: Apparently Anthropic believes that cybersecurity will end and that all vulnerabilities will be discovered in the next two years as models saturate the field, and that these capabilities will diffuse into very small models.
Wow. https://t.co/lt9GPALVVQ
形式化验证从小代码库走向大规模真实项目,AI 辅助审计门槛明显下降。
RT @AnthropicAI: New on our Frontier Red Team blog: using Claude to formally verify software at large scale.
Formal verification can prove that code is free of certain bugs, but historically it has only been feasible for small codebases (or required a lot of expert time).
With AI models, however, this is beginning to change. In collaboration with @theoremlabs, we used Claude to prove security properties in over one hundred real-world open-source libraries over the span of a few weeks.
Read our research in full here: https://t.co/zUyx8CjBEk
🧠 Master Malware Analysis with Sysinternals
Procmon is one of the best free utilities for dissecting live threats. Capture malware behavior, filter OS noise, and spot persistence mechanisms fast.
Watch our full breakdown of top Sysinternals tools:
👉 https://t.co/c48U3cp67G https://t.co/redkgUG1u5
Zero exploitation of php2shell
🎯 Hate searching for memory offsets that break when the game updates?
Source Engine has a function called CreateInterface. Just pass it a string name, and it hands you the core interface pointer instantly.
👉 https://t.co/yU6Q4qe06L https://t.co/6z2VYBMiRm
RT @ivankriznar: @RonMasas Node2Shell 🤝 PHP2Shell
修补前后解压输出不同,能批量测绘易受攻击节点后精准打击。
RT @julianor: Reproduced the Brotli memory corruption bug (CVE-2026-111497) using a simple Node.js + Express app.
Patched and unpatched versions produce different decompressed output, making it possible to remotely identify vulnerable servers. https://t.co/fN4TMrPvNs
手法简单但缺少现成检测规则,可直接转成主机狩猎逻辑。
RT @ipurple: I wrote an article about the technique that was disclosed some years ago by @mrd0x - Custom Extensions, including detection opportunities.
TL;DR: Threat actors may create a custom extension or modify an existing file extension to masquerade a malicious file as a legitimate file or evade Windows SmartScreen.
🖊️ https://t.co/RzLmCRxpnS
主力逆向框架更新,纯本地运行,不依赖外部服务。
ghidra Ghidra_12.2_build — Ghidra is a software reverse engineering (SRE) framework https://t.co/rXy7iw2CX3 https://t.co/d1vOztxnKV
Agent 自动支付场景的信任模型存在系统性问题,影响面延伸到 LLM 工具链。
RT @v12sec: V12 found 25 vulnerabilities in the x402 protocol.
Critical findings included:
- Requests approved without any payment
- Maliciously high requests being paid by default
- Session takeover from relayed login signatures
Here's how. 🧵 https://t.co/0jIv7VpET7
移动端与桌面端用户态利用链的构建门槛进一步降低。
Chernobog now supports arm64e primitives. (On master, not yet released.) https://t.co/lB6VqoiBZB
给出真实暴露规模与攻击者准备度,便于排修补优先级。
RT @Huntio: 🚨 #PHP2Shell (CVE-2026-109618, CVE-2026-109619): everyone is staging the leaked PHP RCE, no one has landed it 🫠
We mapped the exposed PHP footprint and went into the attacker open directories after the Oct 21 leak.
What we found:
→ 683,922 IPs leaking a PHP version in one day of scans, mostly end-of-life builds
→ ~a dozen open-dir workspaces staging php2shell tooling, zero victims or shells in any of them
→ one mass operator sprayed up to 123 servers via a ~97-proxy farm, zero shells
→ scanning started ~20 min after the patch, driven by an existing Mirai-style botnet
→ no public PoC lands code exec on x86-64 yet (OOM corruption vs ASLR)
Patch now: 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35.
Full research + network observables: https://t.co/5R2iX3dipX
RT @joshua_saxe: Thoughts on php2shell and the overall looming crisis in cybersecurity
If you'd been appropriately pricing in that we'd see this and many more celebrity zero-days at an increasing rate, this is a positive update; defenders found this issue, alongside tens of thousands of others in the last year, before widespread exploitation, and it's being patched.
Real attackers will exploit this, but we shouldn't expect a recognizable blip in overall cyber damages in the next couple quarters, because easier initial access to victim networks wasn't a core bottleneck for attackers, and because defenders are better positioned to adopt AI automation than attackers, and are doing so faster; this advantage will persist through at least H1 2027, and possibly longer, IMO.
Why I think this: consider that, in general and on average, defenders have access to default-world capital networks and AI talent, often as a function of how central they are to Internet and societal infrastructure. They have consistent, reliable access to AI inference from open- and closed-weight providers.
Criminal attackers, on the other hand, face the threat of arrest, difficulty accessing AI talent, and unreliable access to AI inference. They're competing for and attempting to retain talent willing to risk arrest and sanctions, and willing to live a life of crime.
Nation-state attackers, meanwhile, operate within military and intelligence bureaucracies that have historically lagged private industry in adopting technologies, from mobile devices to drones. Non-US-aligned nation-state attackers also face challenges in reliably, consistently, and secretly accessing US frontier models.
So, all in all, AI is making offensive capabilities cheaper, but that doesn't immediately translate into damages. At this point, this is a robust finding from the entire 2022–26 period; as in the rest of the economy, we haven't seen a big AI-driven productivity bump among attackers, and attackers are even more disadvantaged than your average business or civilian state agency.
Of course, this won't last forever! How do we exploit our current, limited defense-dominant window? Getting to a good-enough steady state will require creative thinking. I liked @chrisrohlf's piece on eliminating attack surface in OSS applications because it identifies leverage points for eliminating whole classes of risk using 2026-era AI (https://t.co/L2alFLbNs9).
We also need to revisit formal verification, control flow integrity, dynamic taint tracking, and the like, now that AI can make them more practical than they used to be. We also have an enormous overhang of underdeployed defensive technology. Honeypots, honeytokens, sandboxing, multi-factor authentication, and application allowlisting are all less widely deployed than they should be because businesses calculated they weren't worth it.
The AI industry should recognize that heavily gated trusted access programs have failed as a strategy; php2shell was identified by defenders first, and we need more defenders identifying more bugs faster. The defense-dominant window is exactly the moment to pour gas on the fire of diffusion of as-cheap-as-possible AI security capabilities that disproportionately advantage defenders.
If you don't like what this means for attacker access to models, I agree with you! The answer is to solve the quadratic coordination problem among cyber organizations, AI companies, governments, and Internet infrastructure providers by building institutions that identify attacker groups, kick them off inference platforms, and, wherever possible, get them arrested. This is an operational threat intelligence / threat interdiction problem, not a trusted access program problem.
RT @CyberInsidercom: ⚡ Capcom discloses data breach affecting 11.7 million accounts worldwide.
Unauthorized access to CAPCOM ID exposed email addresses, login timestamps, and IP addresses on 11,774,247 records.
Attackers changed passwords on 196 accounts. No credit card data or original user passwords were compromised.
Details ↓
https://t.co/OwFPAELMbU
RT @ZachWeiner: Not an ai apocalypse doomer or whatever, but entering a world where the normal operation of cybersecurity is vast swarms of hacker bots battling vast swarms of defender bots 24/7 at a scale beyond human comprehension doesn't seem like a *great* path forward.
RT @naomibrockwell: At @defcon I interviewed people building all kinds of anti-surveillance tools.
Flock detectors. Rogue cell tower catchers. Bluetooth trackers.
No one’s coming to save us. We must build the resistance ourselves. https://t.co/QDtpr1owu8
说明 PHP 层攻击面正被系统性打通,SAPI 选型会直接影响暴露程度
So, universal RCE for Apache mod_php is easy. For php-fpm it is not, still working on it.
域名先行注册通常是攻击基础设施的前兆,可用于提前布防检测
🚨 𝟰𝟯 𝗽𝗵𝗽𝟮𝘀𝗵𝗲𝗹𝗹 𝗗𝗼𝗺𝗮𝗶𝗻𝘀 𝗥𝗲𝗴𝗶𝘀𝘁𝗲𝗿𝗲𝗱. 𝗖𝗼𝗶𝗻𝗰𝗶𝗱𝗲𝗻𝗰𝗲 𝗼𝗿 𝗖𝗮𝗺𝗽𝗮𝗶𝗴𝗻 ?
Early domain registrations often tell a story before the infrastructure goes live. The question is whether these 43 php2shell domains are simply defensive registrations ... or the first breadcrumbs of a larger campaign.🎣
𝗣.𝗦. The red dots are not decoration. They indicate a relatively @silentpush high-risk rating, and the fact that most of the 43 php2shell-related domains carry that designation makes this cluster even more interesting to watch. 👀
#DomainIntelligence #ThreatHunting 🧙♂️
不依赖具体漏洞的检测思路,对新出现的漏洞同样有效
I took this opportunity to revisit and update my 2022 presentation on post-exploitation detection.
The exploit may be new, or completely different from anything we’ve seen before, but the activity that follows often fits patterns we already understand. Generic detection rules can recognize those patterns without knowing which vulnerability was used. A rule written for one incident can therefore help detect another, years later.
That’s the idea I’ve been talking about for years, and what the presentation explains in practical terms. The slides walk through how to turn an observation into a useful rule, which data you need, and why a match still needs context.
There are examples using Sigma and YARA, a look at how we apply them in THOR and Aurora, and my “Sigma Hall of Fame” with some old favourites :)
https://t.co/tSUGMwpjxG
自建服务与 Agent 出网流量的指纹化检测,可直接用作文档参考
All you need to know about JA3 & JA4 Fingerprints (and how to collect them) https://t.co/rQybrZWySg
RT @cyb3rops: https://t.co/yBSDZvoUYr https://t.co/6F2VhgHKuT
RT @basedjensen: Bruh... DNS infa is fucked. Update your bind boys https://t.co/Gbll8AK5g2
RT @SIGKITTEN: what if we just automatically patched security vulns directly in the bins
https://t.co/vV6hrXEvRn
RT @Ministraitor: Signal Processing And Math For Malware RnD For Fun And Profit - Cocomelonc
#HackLu @hack_lu
https://t.co/E6PfSURZcr
RT @wenhaocha1: Today we are launching FrontierCS 2, the most frontier benchmark for AI agents in computer science R&D. We built 48 tasks from published papers across 13 areas of CS, refining each one with experts in its field. Excited to co-launch FrontierCS 2 with @kaggle @GoogleDeepMind https://t.co/rfWyJ9tFsf
RT @layle_ctf: Introducing: Another Pwn
What's writing your own Wii emulator without also writing your own Wii exploit?
Another Pwn is a savegame exploit for Another Code R, powered by a good old strcpy bug :)
Dropping another one soon, incl. both writeups!
强制签名的环境同样被绕过且波及域控,横向移动门槛显著降低
RT @abdo_mhanni: Crazy cool blog I saw on linkedin about an SMB signing bypass technique
TLDR: SMB re-auth reuses the original signing key and never checks the new identity matches the old. So you sign a session as a low-priv account you control, re-auth it with a relayed privileged login, and get a privileged session still signed with your original low-priv key, which btw is accepted even where signing is required, with DCs included.
https://t.co/G3MWUMfA0f
同一解析器两处缺陷,覆盖路由器与嵌入式 WiFi 固件,含完整幻灯片
Exploiting Broadcom WiFi Across eCos and Linux (@qkaiser)
https://t.co/IU5hOGAYyn
Slide deck: https://t.co/pjbBIytmlI
#infosec https://t.co/8r4oC0K6y4
复现失败多源于此,评估真实暴露面时要先排除现有缓解措施
RT @shotgunner101: It's worth mentioning that for anyone testing their PHP POCs on a linux test device . SELinux can limit its success, aswell as other circumstances like non-default settings or modules being required, or other types of mitigations/protections. https://t.co/l8FBItqaMK
固件加固下仍被取得 root,展示智能家居设备完整数据外流链路
RT @0x0SojalSec: WTF, $3000 Samsung TV has an always-on mic, automatic content recognition, geo tracking, network mapping, and ships your data to Samsung + 400 partners.
Bro Rooted a brand-new 2025 Samsung TV after noticing absurdly targeted ads.
Firmware was locked down, so zero-days it was.
Got a root shell.
then found: always-on voice service, ACR, geo, full telemetry pipeline, and four separate DRM systems.
This isn’t a bug, It’s the product bro.
RT @S1r1u5_: you're underestimating the state space of all possible ways to compromise a company. no amount of astra or mythos tokens is going to fundamentally change the asymmetry anytime soon. it is also very clear that every model is opening up new vulnerability space with no saturation anytime soon. with all the insane vibe coding and expanding agentic attack surfaces, it's only going to get worse.
even if we somehow saturate vulnerability discovery and patching, attackers will move to social engineering, with insanely capable models persuading people to click things, grant access, or make mistakes.
i don't see a future where cybersecurity becomes defense-dominant without just cutting down software, and continuous agents monitoring and stopping attacks across individuals and organizations, and even then, it might require something like 30% of all inference compute devoted to defense
RT @calif_io: Do you know who illustrated the comic on https://t.co/KEUVez9rnN?
Her name is Stephanie Cortes. And her husband is the hacker who discovered php2shell: @lcfr_hax.
This artist-hacker couple has the best story, stay tuned!
WUBBA LUBBA DUB DUB!
Can you guess the vulnerability? 🥒🐍
Wrong answers encouraged. https://t.co/gY6jv4Yhnu
https://t.co/EC9nPMjSWc https://t.co/a4sAg1BjvR
RT @brokenpacifist: mitmproxy: use `--emudhra` to sign TLS certificates 💀 https://t.co/wJJCrfeX2l
RT @anthonyronning: @hardiksd The dirty secret across the entire AI industry is that derivatives (ai summaries) is fair game for data collection.
域内强制认证攻击面收窄,剩余 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 💀💀💀
CVE 通胀直接改变漏洞价值与修复优先级判断,研究产出需重新校准。
THIS!! In all the excitement of AI'ing the vuln hunting process, people forgot to update their own perspectives. Collisions are happening all over the place, because AI. What.. did you think that the 2000% increase in Patch Tuesday CVEs was because everyone got smarter? 🤣
CA 私钥若真可猜,签发信任链整体失效,影响所有依赖其证书的站点。
People weren't joking... the eMudhra P-384 private keys were literally "4" 😂 https://t.co/YsedpobfWZ
收录改名前后截图与开发者身份证据,可直接用于识别移动端订阅欺诈。
RT @privacyis1st: 🚀 I’ve launched App Scam DB — a new home for my investigations into scam apps and misleading App Store listings.
Some apps launch as generic tools, then change their names, icons and screenshots to borrow the identity of brands people trust — while pushing expensive weekly subscriptions.
🔎 I track those changes and examine developer identities, websites and pricing.
📸 Reports include original screenshots, before-and-after comparisons and downloadable evidence.
👥 Written for everyday users, not just security researchers.
Explore the reports 👇
https://t.co/CjuvLhegkA
说明 LLM 结果高度依赖提问者先验知识,做能力评估须控制变量。
I remember when Terry Tao posted a transcript of his ChatGPT conversation about the Jacobian Conjecture counterexample someone said "it's hard to believe he's talking to the same ChatGPT I am" which I think captures it. Same model, very diff results depending on who asks and how
The weird part about this is that it can be hard to pin down exactly what makes the difference. An expert just chatting with a frontier model will still get better results than someone unfamiliar with the topic!
Claude’s memories can include very funny things sometimes. Mine included “wife is named Katya” (nope, that would be my cat)
The tool had to correctly tokenize and parse the C source file, in order to be able to do this.
jobj@intel32:~$ ./lint lint.c
lint.c:17: error: too many lines per function (>15)
lint.c:85: error: too many lines per function (>15)
lint.c:114: error: too many lines per function (>15)
lint.c:158: error: too many lines per function (>15)
lint.c:191: error: too many lines per function (>15)
JB
I am on 4 days of no sleep, trying to save companies from TAs.
@factcheckdotorg Hello, contact me :), it has to do with your AWS keys.
RT @dyn___: In a world of AI slop blogs, presentations, images and write ups...
Calif is an excellent example of how to harness it correctly. Accuracy, Art, Asthetic all supporting excellent AI assisted research. 👏
https://t.co/nUyxQldIrz
Extendimos la fecha de entrega del challenge! Tenes tiempo hasta el 26 de Octubre para enviarlo! El challenge tiene un total de 4 niveles, si no llegaste a completarlos todos envialo igual explicando con detalle todo lo que hiciste hasta la instancia que llegaste.
Todavia estas a tiempo de sumarte a Gecko Academy! 🦎
边界设备配置即凭据仓库,可用作自建设备的排查清单
Group-IB and NyxLab found 70,000+ credentials in k0t's edge-device campaign. The operators decrypted FortiGate configs for LDAP and AD secrets, then deployed AdaptixC2. https://t.co/9c4f2xcz0T https://t.co/tkFTjNO6VA
零检测样本的具体工程手法,可用于补强 macOS 检测规则
RT @moonlock_lab: 1/ We tore apart a #macOS C2 implant that's currently sailing past engines on VT - 0 detections as of today. Shared by @malwrhunterteam.
Written in Zig, and engineered like red-team infrastructure.
Here's what makes it interesting 👇 https://t.co/TpMbBp6q2v
完整解密栈附 C 实现,取证与凭据提取可直接复用
From Boot Key to Plaintext: How Windows LSA Secrets Are Deciphered from the Registry https://t.co/HrH1g4zgDh
可复现的注入手法,红队实现与检测规则都可直接借鉴
''GitHub - epersic/DLLParty: Demonstration of the DLL party process injection technique''
#infosec #pentest #redteam #blueteam
https://t.co/gmTmAp2Zxh
稳定的侧加载技术标记可串联多起事件,适合做狩猎规则
Sophos researchers investigated a cluster of incidents attributed to the BRONZE SANDCASTLE threat group. The most distinctive technical marker for BRONZE SANDCASTLE is its consistent use of Sandboxie DLL sideloading. https://t.co/XNycsMSRWo https://t.co/Sj4awAiWM7
说明在线身份核验仅比对数据存在性,冒名成本极低
RT @kyletorpey: This story shows how hilariously broken online identity verification is from all relevant angles.
1. Your SSN, DOB, address history, etc. are sitting in countless data breaches and data-broker dumps. They’re cheap and widely available to basically anyone who looks.
2. KYC/AML mostly just checks that the data exists and matches a real person. It doesn’t confirm the person signing up is actually the real person behind that identity.
Result: Amanda Smith spent three nights in jail and now faces up to six years in prison over a $1,000 CashApp scam account opened with her SSN and DOB. It wasn't necessarily opened by her, and the phone, IP, device, address, and other details don’t match.
The funniest (and yes, saddest) part is CashApp wouldn't give her information about the account because she can’t prove she’s the owner. Her personal info was good enough to open the account, but not good enough to access it in the future, apparently. To be clear, CashApp is likely just following the law here.
Anyway, we need to burn it all down and start fresh.
RT @S1r1u5_: here is their crazy work, follow them
https://t.co/amYfP3x0NF - @rootxharsh
https://t.co/5pccnzuri6 - @PaulosYibelo
https://t.co/GbEWfPvmbP - @lcfr_hax
https://t.co/7Xj1sQ4NgN - @joaxcar
https://t.co/5Dvwdrk647 - @moyix
https://t.co/00879UNQpl - @hash_kitten
RT @anthonyronning: Anyone wanna take a guess at what’s going on here or has there now been enough indisputable proof that openai is monitoring the logs of high profile experts.
RT @tszzl: this is just wrong: these vulns were found by defenders using Daybreak rather than attackers. It's just evidence Glasswing didn't go far enough, possibly due to capacity constraints. It's also very likely that March Mythos was not as good as Sol/Astra of September
RT @alisaesage: I don’t think the world is ready for the zero day apocalypse that’s upon it.
Cost of entry was the only real constraint on ethics of the game. Given current AI, it no longer holds.
Who pays more for the bug is the only question now.
Critical software vendors that don’t have a good bug bounty program are screwed.
RT @BlWasp_: While everybody is prompting for PHP, recently I ended up having to dump the LSA in a custom way.
I have written a short article on the entire LSA decryption stack, with the C implémentation. 💫
Cross posted here https://t.co/ECtj5iKR5d and here https://t.co/WOXK3lurpL
authentik version/2026.8.5 — Provides open-source SSO and identity provider functionality with SAML, OAuth2/OIDC, LDAP, and RADIUS support for centralized authentication, authorization, and access management. https://t.co/cDLJmFSLbY https://t.co/ljxVlwuOfG
私钥可预测意味着证书信任与固件签名同时被击穿。
RT @IzzatStatus: More private keys by the Indian certificate authority have been discovered. These are all small numbers.
People are suspecting that they interpreted 384 bit keys to mean that they should pick numbers from 1-384 to use as their private keys.
暴露被弃养 IoT 与固件信任链的长期失效面,手法可复用。
RT @singe: eMudhra has two interesting implications for me beyond the obvious browser trust issues.
I'm excited for the opportunities to liberate closed hardware this provides. We know hardware, particularly abandoned IoT devices are unlikely to be updating their revocation lists and root CAs. This means we can potentially intercept previously encrypted comms, or sign previously protected firmware.
I'm also interested in how well the revocation works at a WiFi supplicant level. Rogue RADIUS servers (mana, wpe, eaphammer) can now use validly* signed chains for forged leafs with TLS protected EAP modes. I'm not sure how well the revocations work in that world given the difference in the CA trust model in use there.
本地跑微调模型做漏洞挖掘时,结论可能系统性偏向某一侧。
Don't Let Abliteration Abliterate Your Bug Hunting: Discovering Verdict Bias in Uncensored Models - @clearbluejar
https://t.co/xaMhQLhMkn
新硬件首个公开越狱链,硬件层逃逸思路可迁移借鉴。
RT @pepsipu: i jailbroke the nintendo switch 2
so i modded cinnamoroll, peter griffin, hatsune miku, and more into Mario Kart World, a switch 2 exclusive
now watch my friends and i get cooked by bots
learn more and get the exploit https://t.co/ykjgyfrFRp https://t.co/BOcFhejRz1
说明前沿模型已用于发现真实漏洞,AI 挖洞进入实战阶段。
RT @Hesamation: wait, PHP was actually scanned by Anthropic’s Claude Mythos earlier this year. they also had access to OpenAI’s Daybreak Red for validating exploits.
the PHP Foundation revealed this JUST yesterday.
keeping frontier cyber models in the hands of a selected few doesn’t seem to be working well for the internet.
https://t.co/rangh8iW6M
复现者最需要的踩坑记录与可用链条,能省下大量验证时间。
RT @Dinosn: Beyond lab setup the best so far that I could reach to real exploitation on PHP is hitting OOM. No markers, no callback. Best resource seen https://t.co/xUJ5PjVEJZ (initial aslr-on chain), highest promising work, https://t.co/1GmBLpfCAH (don't go for the paid module has nothing) and of course the latest update from Calif https://t.co/0mU4t6FWC3
RT @SinSinology: To teach a lesson,
After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought https://t.co/hQYMb3AZlk before wiz could pull the same stunt again.
A big budget can buy a domain. It shouldn't buy someone else's research credit.
If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve.
Hack the planet. Credit the researchers.
interesting, and concerning(?). i wonder if successful cyber trajectories are being continuously fed back into training and new checkpoints rolled out rapidly.
gost v3.3.2-nightly.20261021 — GO Simple Tunnel - a simple tunnel written in golang https://t.co/U06lJOlcrO https://t.co/76scDl0FE3
QUIC 实现广布于网关与 CDN,需确认所用库是否受影响。
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
认证后即可 RCE,且该组件多位于内网管理平面,横向价值高。
Post-auth RCE vulnerability in Cisco Smart Software Manager (CSSM) (@starlabs_sg)
https://t.co/0aNFl45LYD
#infosec https://t.co/pQSq06bF7x
可自托管部署,作为暴露 PHP 服务前的低成本过滤层。
SafeLine v9.4.3 — Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption. https://t.co/lik6ortPHj https://t.co/A2vQNOMp6l
固件/IoT 中 WASM 逆向的实操流程,公开资料较少。
https://t.co/95miTdGsja next one from my blog! #reverse #engineering series! while everyone is discussing their love for PHP enjoy this ❤️
https://t.co/ILvbfgxIvv
#wasm #aot #hacking #IoT #firmware #research #decompiling https://t.co/dAvbteXMH2
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
RT @Dinosn: Leaving this here, PHP 8.5.12 security patch is incomplete. ( needs further validation ) https://t.co/iVLBm2gUUZ
RT @earakely: We're making rapid iterations on this in the coming weeks. The goal is that REA can be run on your laptop to produce an RL env of your computer and the work you do on it.
is this still not clear?? i want to bring this up again
optimistically, lets assume cyber is defense dominant and exploitable vulnerabilities are finite and exhaustible.
then, give the fucking models to as many good security researchers as possible and let them exhaust the attack surface.
pessimistically, i think cyber is offense dominant. the sin of complexity, vibe coding making it worse, and increasingly capable models potentially opening up entirely new vulnerability space, and you need to secure everything. then, your best bet is attack surface reduction, formal verification and secure by design, but thats a fever dream and aint happening anytime soon.
so, again, give the fucking models to as many good security researchers as possible and let them find and eliminate as many attack paths as they can.
either way, walled gardens are counter productive.
澄清 AI 漏洞发现的攻防归属,避免误判当前威胁水位。
this is just wrong: these vulns were found by defenders using Daybreak rather than attackers. It's just evidence Glasswing didn't go far enough, possibly due to capacity constraints. It's also very likely that March Mythos was not as good as Sol/Astra of September
无细节但有结论,指向 IoT 设备高影响缺陷,值得跟进原帖。
RT @pedrib1337: Clanker verified and PoC'ed ☑️
This is a disaster for IoT https://t.co/fcRSAOEDLB
模型访问策略直接影响攻防双方能力差,可观察社区共识走向。
btw, i think dario was right about the cyber risks of proliferating these models freely on the internet, but wrong about how access should be distributed.
looking back at this tweet, glasswing was directionally the right approach, except it remained a walled garden for a select few. openai got this part right by giving broader access to legitimate security researchers.
退出开关实际无效,消费级设备遥测难以靠设置关闭。
RT @IntCyberDigest: ❗️ Samsung and Vizio smart TVs kept contacting the servers that track what you watch after users opted out, Northeastern University researchers found.
On Vizio the opt-out had no visible effect, even with the TV idle. https://t.co/DWzBN3YCFB
RT @filpizlo: Brotli works great in Fil-C.
I know that Fil-C isn’t as fast as Yolo-C yet. But is the perf worth the risk?
Ask yourself and think about it
RT @WatsonLadd: @i0n1c More like first discovered 2004, definitely 2020, extremely in 2024 but never properly fixed until 2026
obligatory @_NathanCalvin tweet! but, i generally think, we normies are fine, there is no money to be made from us. https://t.co/dozeBzRGSI
提示该漏洞公开前已被在野利用,真实修补窗口比公告更早。
Almost tempted to publish the heavily obfuscated version of the PHP exploit that we caught in one of our honeytraps 4 months ago. But what's the point?
I never like to see code that we wrote/discovered end up used by ChiComms and Russians (even for conceptual inspiration)
模型能力准入差正在改变攻防双方的漏洞挖掘节奏。
openai restricted astra access to security researchers, i think it is a mistake. there is a temporary capability gap that defenders could take advantage, and we shouldn't waste it.
put researchers through daybreak, vet them all you want, but remove the red/blue distinction. give 1000 vetted researchers access to the best models and monitor the hell out of their usage to detect abuse.
不同厂商模型在漏洞挖掘上的可用性差距,影响工具选型判断。
RT @rootxharsh: 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.
曝光事件可能在披露后数周持续新增,日志回溯仍有价值。
You will see a lot more of this as people get a chance to sift through the relevant telemetry https://t.co/VeElQsCK2R
按 RFC 缓解措施部署即可规避该 DoS,避免误判为协议层漏洞。
RT @bedros_p: @grhmc @4A4133 @dpc_pw Excessive memory causing a crash on 2GB instances :P
IMO this whole release should be reworded, this is a well known issue within QPACK and the RFC explicitly states mitigations, the bugs are just non spec-compliant software
It's good work, but it's not a bug within QPACK/QUIC
RT @bl4sty: anthropic has employees installing mics in their own offices.. openAI had some questionable situation with the navier stokes discovery. we need to stop sending them good context..
.. although most collisions are probably just people rolling the virtual dice in a similar way ;)
https://t.co/He1RduCEVR
https://t.co/qeNJ1iGBvG
只有悬念没有证据,价值取决于后续公布的遥测细节与样本。
As I was saying…
You will see more of this as people go through the relevant telemetry https://t.co/9zmgssYqz7
phpbleed 是该漏洞族的新命名,可用作后续追踪与检索的线索。
RT @SinSinology: To teach a lesson,
After Wiz rushed to buy php2shell domain and use its marketing machine to steal the spotlight, I spotted "phpbleed" in a recent Calif tweet and bought https://t.co/hQYMb3AZlk before wiz could pull the same stunt again.
A big budget can buy a domain. It shouldn't buy someone else's research credit.
If you have contacts at CISA or in the press, do the right thing: make sure the researchers who actually did the work get the recognition they deserve.
Hack the planet. Credit the researchers.
As I was saying…
You will see more of this as people go through the relevant telemetry https://t.co/3LYmulc0uL