Megatron LLM Hub
All digests
Twitter

推特安全流

Top7

Windows 0-day HardBreacher 公开,针对卡巴斯基产品。

0-day 细节公开,PoC 已发布,影响面广。

RT @cr3ghost: 0-day dropped. Another fresh Windows security release from @MSNightmare2000. RoguePlanet. GreatXML. LegacyHive. ShieldBreak. Now: HardBreacher. At this point, if you do Windows internals, vulnerability research, reverse engineering, red teaming or detection engineering, you probably want to stop scrolling and look at this one. https://t.co/UXkOhyhx27 #0day #WindowsSecurity #VulnerabilityResearch

0daywindowspoc @cr3ghost source ↗

Metasploit 发布 PaperCut 0-day 利用模块,绕过紧急补丁。

活跃利用的 0-day,PoC 已集成到 MSF,需立即排查。

RT @stephenfewer: We have published our @metasploit exploit for the recent PaperCut MF and NG zero-day (CVE-2026-81578 + CVE-2026-82078) that is being actively exploited in-the-wild. Module supports both MF and NG editions, and all supported product versions 26.x, 25.x, 24.x. Bypasses vendor emergency patch v1. Emergency patch v2 successfully remediates the chain. Module also has platform agnostic Java payload support (and that will be in-memory on 26.x targets), along with OS command based payloads. https://t.co/Qg5hvnWYFT

cvepocrce @0xocdsec source ↗

npm 包 openapi-react-query-codegen 遭供应链攻击。

150k 周下载量,恶意版本执行任意代码,需立即检查依赖。

RT @DailyDarkWeb: 🚨 NPM SUPPLY CHAIN ATTACK: OPENAPI REACT QUERY CODEGEN COMPROMISED Socket researchers have identified an active supply-chain compromise affecting the npm package: @7nohe/openapi-react-query-codegen The package receives roughly 150,000 weekly downloads, and attackers published 10 malicious versions on August 28, 2026. * Malicious releases were pushed across every maintained release line * The compromised versions executed attacker-controlled code during installation * The payload targeted cloud credentials, npm/package-registry credentials, GitHub Actions secrets and AI-agent configuration * The malware included self-propagation functionality consistent with the "Mini Shai-Hulud" campaign * It could poison npm, JFrog and RubyGems packages * It contained optional PyPI typosquatting functionality * It could modify GitHub Actions workflows and harvest CI/CD secrets * It included persistence mechanisms for macOS and Linux * It could propagate to reachable systems over SSH One of the most important findings: ⚠️ ALL 10 MALICIOUS VERSIONS HAD VALID NPM PROVENANCE ATTESTATIONS. The attacker abused a GitHub Actions publishing workflow triggered by issue comments. According to Socket, any GitHub account could comment: npm publish on a pull request and cause code from an untrusted fork to be published using the repository's trusted OIDC identity. As a result, the malicious packages appeared to have legitimate provenance. Socket warns that: npm audit signatures will NOT flag these releases. Affected versions include: * 0.5.4 * 0.5.5 * 1.6.3 * 1.6.4 * 2.2.1 * 2.2.2 * 3.0.3 * 3.0.4 * Two malicious 0.0.0 prereleases Known-good versions per maintained branch: * 0.5.3 * 1.6.2 * 2.2.0 * 3.0.2 ⚠️ IMMEDIATE ACTION: Organizations that installed an affected version should treat the developer machine or CI runner as compromised. Socket recommends: * Isolate affected systems * Rebuild developer machines and CI runners from known-clean images where possible * Rotate GitHub, npm, cloud, registry and CI/CD credentials after containment * Check lockfiles and SBOMs for affected versions * Clear package-manager caches * Reinstall from a clean lockfile using a known-good version ⚠️ Analyst Note: This incident exposes an important limitation of software-supply-chain provenance. A valid signature or provenance attestation can prove WHOSE WORKFLOW produced an artifact. It does not necessarily prove that the SOURCE CODE entering that trusted workflow was trustworthy. In this case, the attackers didn't need to steal the maintainer's signing identity. They found a way to make the legitimate publishing infrastructure sign and distribute attacker-controlled code. That is a particularly dangerous failure mode for modern CI/CD supply chains. Source: Socket Research Team https://t.co/dY1JEHXn98 #DDW #SupplyChainAttack #npm #GitHub #CyberSecurity

供应链npm恶意代码 @0xocdsec source ↗

OEMpocalypse 研究:通用 Linux 内核漏洞实现安卓 root。

跨设备安卓提权新思路,影响 Pixel/Galaxy 等主流机型。

RT @calif_io: New research: OEMpocalypse Now! Our own Lukas Maar spent a few weeks pursuing one question: How do you turn a normal Android app into root access across as many phones as possible without rewriting the exploit for every model? Generic Linux kernel bugs offer broad coverage: one exploit can target both Pixel and Galaxy. But bugs that survive years of auditing often provide only constrained slab-level primitives, forcing the exploit into heap grooming and per-device tuning. Chipset drivers offer stronger primitives. A GPU or DSP driver pins and maps entire pages for the device, giving the attacker page-level access. But coverage follows the silicon, and each OEM ships several chipsets across its lineup. Lukas chose a third target: the code Samsung, Xiaomi, and Oppo build on top of Android. These components belong to One UI, HyperOS, and ColorOS rather than the underlying hardware, so they span an OEM's lineup regardless of chipset. The strategy exploits a page use-after-free in an OEM kernel driver. If SELinux restricts the driver to a privileged domain, an OEM sandbox escape reaches it first. A stale mapping to a freed physical page bypasses much of Android's kernel hardening. It requires no KASLR leak and hijacks no control flow, leaving slab protections and CFI irrelevant. The same page-reclamation code worked unchanged from kernels 5.15 through 6.12. Lukas built the chain three times, once for each OEM. The exploits run on a Galaxy S26 Ultra, Galaxy S26, Xiaomi 17, Oppo Find X9 Ultra, and OnePlus Ace 6 Ultra, all running stock July 2026 firmware with locked bootloaders. The write-up includes demo videos. Part 1 explains the strategy, its reasoning, and its tradeoffs. Parts 2 through 4 present each OEM-specific chain. Read it at https://t.co/hTNqoqWWMa.

安卓提权内核 @0xocdsec source ↗

CPython 内存安全漏洞逃逸沙箱,攻破 Grafana Cloud。

沙箱逃逸实战案例,对云安全有直接参考价值。

RT @runsybil: We used a memory safety bug in CPython to escape a sandbox and hack a @grafana Cloud instance. Read how we did it: https://t.co/jhx8WIl5m3

沙箱逃逸python @0xocdsec source ↗

Windows 内核 0-day LPE 已报 MSRC,细节未公开。

内核提权 0-day,虽未公开但需关注补丁状态。

RT @gr4ss341: Another Windows kernel 0-day LPE, reported to MSRC. Looks like they’ve been pretty busy lately :D https://t.co/TjqS6NopmE

0daylpewindows @0xocdsec source ↗

Debian netfilter UAF 漏洞 CVE-2026-80714,PoC 公开。

影响最新 Debian,PoC 已公开,需评估暴露面。

RT @cybermeowfia: Today's exploit is for the latest Debian, a UAF in netfilter: CVE-2026-80714. It was introduced in Jul 2010 and fixed upstream in Jul 2026. Discovered and exploited by the NebuSec security pipeline. Exp source code: https://t.co/d7p8pHR5dF https://t.co/jZ3QkY6PX6

cvepoc内核 @0xocdsec source ↗
Must-see1

JFrog Artifactory 认证绕过 CVE-2026-82329 被复现。

可获管理员 token,影响 CI/CD 供应链安全。

RT @h4x0r_dz: I have reversed and reproduced CVE-2026-82329, the JFrog Artifactory auth bypass that hands attackers a full admin token" Is this a backdoor or a vulnerability xD

cve认证绕过供应链 @0xocdsec source ↗
Recommended15

Pixel 11 移除 ARM MTE,GrapheneOS 移植受阻。

硬件安全特性倒退,影响安卓生态内存安全防护。

RT @GrapheneOS: We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money. ARM hardware memory tagging (MTE) is used by GrapheneOS across the entire base OS including the kernel and every standard base OS process. It's only temporarily disabled for a few device-specific processes. It greatly improves protection against nearly all remote exploits and many local exploits. Pixel 8 launched with hardware MTE support in October 2023. We integrated it into our hardened_malloc project and began using it across the OS later that month. Android and the Pixel OS never started using it by default. Android Advanced Protection Mode in Android 16 enables it for a few processes. Apple's Memory Integrity Enforcement (MIE) is an always enabled feature on the iPhone 17. It's simply a high quality implementation of MTE using the latest standard extensions. It uses MTE in the most secure mode in the kernel and a large portion of userbase. They did a very good job integrating it. Apple's MIE and Android 16+ AAPM don't use MTE for user installed apps unless those explicitly opt in. GrapheneOS enables it for more apps automatically and has a toggle for users to opt-in for every user installed app. There's a per-app toggle to opt-out for incompatible apps which is uncommon. Neither iOS or Android encourage app developers to opt into MTE and other more aggressive security features used in the base OS. Apple's docs warn developers of performance and stability issues. Even Signal doesn't opt-in. Our approach enables forcing using MTE in the standard allocators regardless. Pixel 11 does have security improvements including moving to post-quantum secure verified boot (ML-DSA) and replacing Samsung Shannon IMS with AOSP IMS. Titan M3 should significantly improve protection against data extraction in Before First Unlock state. It's too bad they ruined it by cutting MTE. Pixel 11 series is a lot more expensive for an incremental improvement to the CPU, the same underpowered GPU and reduced RAM for the Pro base models. They finally caught up to the last generation of Qualcomm cellular radio. It's overpriced, the upgrades aren't impressive and losing MTE is appalling. Compared to the Pixel 11, a Snapdragon 8 Elite Gen 5 has ~40% higher single threaded CPU performance, ~80% higher multi threaded performance, over 100% higher GPU performance and a far better cellular radio. It also finally has MTE. The next gen is what will be in the first Motorola with GrapheneOS. Pixel 9a and earlier (including Nexus devices) were the Android Open Source Project reference devices. Pixel support was removed from AOSP with Android 16. It's now harder to support Pixels than many other devices and massive progress towards open source firmware and driver libraries was discarded. Compared to the stock Pixel OS, GrapheneOS ships AOSP patches months earlier and Linux kernel patches many months earlier. However, we rely on them for firmware and most driver updates. We also want to move to new kernel branches earlier. These things can be improved with our Motorola partnership. We strongly recommend against buying Pixel 11 devices. Pixel 8, 9 and 10 have much better overall security for GrapheneOS. Pixel 10 is cheaper with similar hardware and MTE. Pixel 11's Titan M3 should improve BFU security for users without a strong passphrase, but losing MTE craters AFU security. We haven't determined what to do about this situation. It may be best for us to skip the Pixel 11 series devices. We can shift our focus entirely to the upcoming Motorola devices instead. Pixel 10a was really a 9th gen Pixel, so hopefully the Pixel 11a does the same with 10th gen and includes MTE.

安卓硬件安全mte @0x64616e source ↗

GrapheneOS 反驳 MTE 价值被低估,强调内存攻击现实威胁。

关于 MTE 重要性的权威观点,影响安全决策。

RT @GrapheneOS: https://t.co/X0imidSWau This article has a poor assessment of the value of MTE and the importance of protecting against memory corruption vulnerabilities. These attacks are not theoretical and are definitely not only highly targeted as is often portrayed. Exploits are being widely deployed and neither Apple or Google are reliable sources on how widely they're being used. Their consistently misleading claims on the prevalence of exploitation are based on twisting incredibly incomplete information to paint their products in the best possible light. A developer without extensive expertise can develop working local and even remote for stock Pixels in weeks with the help of a frontier AI model. Pixel 11 cannot be considered AI ready devices when they're built for a world without the massive impact of AI models on security on the present. It's clearly going to improve over the next 7 years and the Pixel 11 is incredibly ill-prepared for it. Google isn't much of an AI company if they aren't going to build products capable of providing reasonable protection from AI accelerated exploits. MTE isn't only for probabilistic protection. It provides deterministic protections. We dynamically exclude the adjacent tags for a slot and the previous tag used for the slot. We statically exclude 0 as a reserved tag for free data, metadata, etc. That's 100% reliable, not 15/16. FEAT_MTE4 (EMTE) which was shipped by the iPhone 17 as part of their initial MTE support adds support for enforcing memory tags for untagged memory (FEAT_MTE_CANONICAL_TAGS). For userspace, it means untagged memory is treated as being tagged with the typically reserved 0 tag. For Android and iOS, nearly all remote exploits involve memory corruption. MTE with FEAT_MTE4 and protection against side channels as the iPhone 17 has provided is the best available defense with a low cost. Pixels had MTE available long before iPhones and could have advanced it. HWASan provides similar security to MTE for code compiled with it at the cost of around 100% CPU overhead and 25% memory overhead. Unlike MTE, it can't protect code not compiled with it. It does have the advantage of MTE not yet coming in an 8 bit form. https://t.co/ADUu3lSpUm Snapdragon 8 Elite Gen 5 has MTE, ~40% faster singlethreaded and ~80% faster multithreaded performance. Comparing HWASan on Tensor G6 to MTE on Snapdragon 8 Elite Gen 5 with negligible overhead would be fun. One way of looking at the Pixel 11 dropping MTE is that it's adding around 100% overhead for reasonably secure software. That's quite a performance loss for hardware which was already not providing competitive performance. Pixel 11 adding post-quantum secure verified boot is not currently useful and likely won't be useful before the end-of-life of the Pixel 11. It isn't the same as key exchange where data can be captured now and decrypted later. Android's standard disk encryption has always been post-quantume secure. Adding this for verified boot is a forward looking improvement but it doesn't make up for losing MTE. Titan M3 may have improved security in other ways but it's hard for them to show that without finally following through on their commitment to open sourcing the firmware and hardware for it. Titan M based on OpenTitan is not the same as them open sourcing it. Google could add back Pixel support to AOSP in a day and could quickly follow through on their commitment to open sourcing the Titan M. Their commitment was not moving to it being based on OpenTitan but rather open sourcing the firmware for the Titan M1 and both firmware+hardware for the Titan M2. They committed to 7 years of updates for the Pixel 9a and that includes AOSP updates since it was sold as an AOSP reference device. They cannot retroactively restore MTE support on the Pixel 11, but they can address these things and come out looking much better than they currently do. Google made a huge mistake with the removal of MTE instead of improving it to match or exceed the iPhone 17. Pixel 11 is incredibly ill-prepared for the age of AI models changing the security landscape. It's a huge downgrade for overall security from the Pixel 10 and it cannot be fixed until the Pixel 12. Google hopefully has time to get MTE added back for the Pixel 12. They're doing an increasingly poor job shipping the rapidly growing number of security patches and need far better systemic security protections simply to defend well against the already known vulnerabilities let alone the unknown ones. They should stop laying off so many engineers and should start taking the impact of AI on security seriously considering how much they brand themselves as an AI company.

安卓硬件安全议题 @0xocdsec source ↗

疑似 Safari 0-day 存在,提示不要访问某网站。

可能影响 macOS/iOS 用户,需保持警惕。

RT @PaulosYibelo: Good morning, seems some ai ppl are going crazy learning ai's can hack and writing insane bs. I personally have been having time of my life with my intern ai hackers for over a yr now lol. Anyways, Pls don't visit https://t.co/HuWwuCDcWE 🌚, there may or may not be a safari 0day https://t.co/nOnBETHJC2

0day浏览器safari @0xocdsec source ↗

AD-PathFinder:BloodHound CE 攻击路径映射工具。

开源工具,提升 AD 攻击面可视化效率。

RT @r1cksec: Attack path mapping for Active Directory, ADCS, SCCM, and MSSQL using BloodHound CE + OpenGraph data. https://t.co/yw2cy3fEUn #infosec #cybersecurity #redteam #pentest #opensource

工具ad攻击路径 @0xocdsec source ↗

卡巴斯基产品漏洞被 HardBreacher 利用,已修复。

安全软件自身漏洞,需确认更新状态。

"Contacted by SecurityWeek, Kaspersky said the underlying issue has been resolved. "The corresponding fix is delivered via an automatic update, or users can trigger a database update manually,” Kaspersky stated." https://t.co/09maFab94A

cve杀软0day @artem_i_baranov source ↗

event_log_manage BOF:控制 Windows 事件日志。

防御规避新技巧,红队可复用。

RT @atomiczsec: fun weekend experiment, trying to control Windows Event Logs and their channels through a BOF...it went pretty well: ✅released event_log_manage which can inspect create write clear destroy event files, useful for defense evasion* or command and control The idea from @BrinklesBB for this BOF was to emulate a adversary "...putting the shellcode into Windows event logs..." for execution you can now replicate this behavior and perform recon through one BOF, link in replies

工具windows防御规避 @0xTriboulet source ↗

AiTM 钓鱼活动针对医疗和学术机构,传播迅速。

医疗行业需立即排查,有 IOC 可检测。

🚨AiTM Phishing Campaign Propagating Across Healthcare and Academic Medical Institutions If you are a cyber defender working in healthcare sector or MSP with healthcare sector clients, you better start scanning your EmailUrlInfo for sites[.]google[.]com/view/ as it is now propagating across healthcare pretty quick. Firstly it is a Sneaky2FA and a compromised account (Org A) sends an initial phish and a user (Org B) clicks the trusted-looking links, once Org B user session token is captured, it is then use to send phish to Org C and so forth. https://t.co/zgTcJSr6n5 I have used my @anyrun_app Intelligence to create a query lookup for those sites[.]google[.]com/view/ tagged with threat name Sneaky2FA, you can use this IOCs to scan against your URL in EmailUrlInfo. If you are in healthcare sector, you would probably get some hits.🫡 Download https://t.co/ml8gIiK9QF_IOCS.txt under IOCS Folder: https://t.co/GBrb6MmVzK #threathunting #Sneaky2FA

钓鱼医疗ioc @0x534c source ↗

Vulnify:给 AI Agent 提供 CVE 知识库。

结合 AI 与漏洞情报,提升自动化渗透能力。

Vulnify: Giving Your Agents a CVE Brain - Brandon McGrath https://t.co/xc9HztV4GS

ai_agent工具cve @pentest_swissky source ↗

滥用 Text Template (.tt) 文件的紫队手册。

新攻击面,检测策略详细。

RT @ipurple: Earlier this week, I published the Purple Team playbook for abusing Text Template (.tt) files. If you’re hunting this technique, MSBuild is the loudest of the T4 binaries (Image Load + File Creation). 🔍 𝑫𝒆𝒕𝒆𝒄𝒕𝒊𝒐𝒏 𝑺𝒕𝒓𝒂𝒕𝒆𝒈𝒊𝒆𝒔 ✅️ 𝐏𝐫𝐨𝐜𝐞𝐬𝐬 𝐂𝐫𝐞𝐚𝐭𝐢𝐨𝐧: TextTransform.exe, TextTransformCore.exe, t4.exe & msbuild.exe ✅️ 𝐌𝐨𝐝𝐮𝐥𝐞 𝐋𝐨𝐚𝐝𝐬: 𝑴𝒊𝒄𝒓𝒐𝒔𝒐𝒇𝒕.𝑽𝒊𝒔𝒖𝒂𝒍𝑺𝒕𝒖𝒅𝒊𝒐.𝑻𝒆𝒙𝒕𝑻𝒆𝒎𝒑𝒍𝒂𝒕𝒊𝒏𝒈*.𝒅𝒍𝒍 DLLs ✅️ 𝐅𝐢𝐥𝐞 𝐂𝐫𝐞𝐚𝐭𝐢𝐨𝐧: T4 and output files under 📁 𝑪:\𝑼𝒔𝒆𝒓𝒔\<𝒖𝒔𝒆𝒓>𝑨𝒑𝒑𝑫𝒂𝒕𝒂\𝑳𝒐𝒄𝒂𝒍\𝑻𝒆𝒎𝒑\ https://t.co/PHnhxu8HC5

紫队windows攻击手法 @ipurple source ↗

BintracerLabs:macOS 恶意软件分析沙箱发布。

macOS 分析工具稀缺,值得尝试。

I just released the first public version of @BintracerLabs, a malware-analysis sandbox focused on macOS. Bintracer can: - Detonate Mach-O binaries, app bundles, and dylibs - Extract DMG and PKG files - Analyze JXA, AppleScript, Python, Perl, and shell scripts This project is still early, but I can't wait to see what y'all think!

工具macos恶意软件 @kyleavery source ↗

Blackstorm Security 免费发布 1600+ 页漏洞研究。

高质量学习资源,覆盖内核、浏览器等。

If you're new to exploit development, reverse engineering or vulnerability research, bookmark this before buying another course. Blackstorm Security has published 1,600+ pages of research for FREE. Windows kernel exploitation. Driver reversing. Patch diffing. Chrome / V8 / WebAssembly. Hyper-V. macOS / iOS internals. Modern mitigation bypasses. Real CVEs taken from root cause to working exploitation. Their CVE-2024-30085 series alone spans hundreds of pages and multiple exploitation strategies. This is the kind of material that teaches you how vulnerability researchers actually think, not just how to run tools. 19 research papers. 1,657 pages. Free. Start here: https://t.co/wDftgmamHH Author: @ale_sp_brazil Focus on the techniques not the tools (X64DBG, GHIDRA/IDA, WINDBG, GDB GEF) #ExploitDevelopment #ReverseEngineering #VulnerabilityResearch

学习资源漏洞研究免费 @cr3ghost source ↗

ysonet:.NET 反序列化 payload 生成器。

红队测试 .NET 应用的好工具。

ysonet — Deserialization payload generator for a variety of .NET formatters https://t.co/JlfDua1RNr https://t.co/8KQ1REBLJG

工具反序列化dotnet @KitPloit source ↗

nl-kat-coordination:模块化网络扫描框架。

集成多工具,提升扫描效率。

nl-kat-coordination — Modular network scanning framework that integrates diverse tools and external databases to detect... https://t.co/43PinMdY3w https://t.co/RNn0VVM4Ck

工具网络扫描 @KitPloit source ↗

ditto:混淆 PowerShell 和 JavaScript 脚本。

红队工具,可绕过检测。

ditto — Obfuscates PowerShell and JavaScript scripts using tree-sitter-based parsing with multiple configurable impostor profiles for stealth, size,... https://t.co/gQkrCORh8f https://t.co/RrTgXs0Rht

工具混淆powershell @KitPloit source ↗

通过书签和扩展攻击 llama.cpp 本地 LLM。

本地 AI 安全新攻击面,与意图直接相关。

RT @G3tSyst3m: Just wrapped up my latest blog post! In short: We explore same-origin attacks using bookmarklets and browser extensions to coerce an already running instance of llama.cpp (the local LLM inference engine) 🦙to execute commands of our choosing. https://t.co/NKMApEkxIg

llm浏览器攻击手法 @kernullist source ↗
More107

bitfalls 发布安全相关文章(链接未解析)。

可能涉及重要漏洞或技术分析,需点击查看。

RT @bitfalls: https://t.co/IUOPO4dkoD

议题 @0xocdsec source ↗

JSCeal:V8 字节码混淆恶意软件研究博客发布。

恶意软件分析技术,对检测有参考价值。

RT @hasherezade: My research blog about #JSCeal is finally out! It was quite a journey. I hope you will like it! // #V8 #bytecode #malware #deobfuscation

恶意软件v8反混淆 @0XDbgMan source ↗

Anthropic 打击被劫持账户挖矿 AI token。

AI 账户安全事件,影响使用 AI 服务的用户。

RT @TheRegister: Anthropic cracks down on hijacked user accounts mining AI tokens https://t.co/Uum3fJrE5l

ai账户安全事件 @artem_i_baranov source ↗

Qualcomm BootROM 漏洞利用,绕过安全启动链。

影响安卓设备底层安全,研究价值高。

Exploiting Qualcomm BootROM to bypass the secure boot chain (slide deck, BH Asia '26) https://t.co/X0cBoWQLIA #infosec https://t.co/7V3nU7ZgVQ

固件安卓安全启动 @0xor0ne source ↗

kernelstub 将发布 omarchy 的 0-day。

可能涉及新漏洞,值得关注。

Hi, will be releasing some 0days for omarchy :).

0day漏洞预告 @kernelstub source ↗

NVIDIA GPU 组件和 Avast 沙箱 0-day 公开。

涉及主流安全软件,PoC 公开需关注。

RT @cr3ghost: Two more fresh 0-day drops from @MSNightmare2000. GreenSection: NVIDIA user-mode GPU components, memory corruption / OOB write. PrettyPrague: Avast / Gen Digital sandbox EoP to SAM dump + SYSTEM. Red teamers: BYOVD isn't the only path to privileged execution. Blue teams + threat intel: public PoCs shorten the path to operational abuse. Start understanding the telemetry before these techniques show up in tooling. https://t.co/qIAoCBYUtY https://t.co/oqHEV7uEnf #0day #VulnerabilityResearch #ThreatIntel

0daynvidia杀软 @cr3ghost source ↗

PatchGuard 研究笔记公开,记录结构监控。

内核安全研究资料,对逆向有帮助。

I’ve started my PatchGuard research. Here are the first notes I’ve taken. I’ll keep updating this document over the next few days https://t.co/1XCaFjcF83 The main goal of this research is to document all the structures monitored by this protection, at least for my Windows build

内核windows研究 @Salsa12__ source ↗

两名澳大利亚人因开源软件投毒被捕,窃取 50 万凭据。

供应链攻击真实案例,警示开源依赖风险。

RT @USEmbAustralia: A joint @FBI, @AusFedPolice and @WA_Police investigation has led to the arrest of two Western Australian men charged with allegedly hiding malicious code in open-source software, harvesting 500,000+ credentials and compromising 1,000+ organizations worldwide. A powerful example of U.S.-Australia law enforcement cooperation and our shared commitment to combating the growing threat of cybercrime. https://t.co/sT0LC7r9na

供应链开源事件 @J3rge source ↗

RedLotus:Rust 编写的 Windows UEFI bootkit。

现代 bootkit 技术,绕过 DSE,研究价值高。

RT @5mukx: RedLotus is a Rust based Windows UEFI bootkit that executes before ntoskrnl.exe to bypass DSE and manually map unsigned kernel drivers. A research focused PoC demonstrating modern bootkit techniques and low level rust development. by MemN0ps Blog:- https://t.co/YKY5KN6DAK https://t.co/w1HsZHF3GD

bootkitwindowsrust @5mukx source ↗

Multikernel 首次公开版本发布。

新内核架构,可能影响未来安全研究。

RT @Itsfoss: Multikernel has got its first public release, but it isn't geared towards desktop users. https://t.co/9sOUzOqeow

内核新架构 @0xocdsec source ↗

ultralight-AES:极简 AES 实现。

学习加密实现的好材料。

RT @oneandonlyhusam: ultralight-AES The smallest implementation of AESin C I can think of. Made as a follow up to my tweet yesterday. This implementation is of AES-128 in ECB mode so its not really the most secure implementation, that would be CBC. Goal was simplicity. https://t.co/4abzsGEMCM

加密aes代码 @0xpwnie source ↗

用 Claude Code 逆向 PaperCut 0-day 的文章。

AI 辅助漏洞分析案例,有参考价值。

RT @Kevin2600: https://t.co/2J8asu4Fzs

ai逆向cve @0xocdsec source ↗

MFA 疲劳攻击案例:WebView 恶意软件窃取会话。

真实攻击案例,展示 MFA 绕过手法。

The user kept getting MFA prompts he did not request. He denied all of them. Normally, you would assume somebody had his password and was just trying their luck. But this one felt different. We checked the sign-in logs and saw several attempts against his Microsoft 365 account. His password was changed, sessions were revoked, and we moved on. Then the MFA prompts started again. That was when we decided to look at the laptop properly. While checking the running processes, I found: WebViewHost.exe The name looked believable because Windows and Microsoft applications use WebView components all the time. But this one was running from: C:\Users\michael\AppData\Local\Microsoft\WebView\WebViewHost.exe I checked the signature. Unsigned. That already looked bad. Then I checked persistence and found a scheduled task called: Microsoft WebView Update It was launching the same executable. So now we had an unsigned Microsoft-looking binary that was starting automatically. I went through the Sysmon logs next. Around the same time the program appeared on the laptop, it created temporary files called: login_db.tmp and cookies_db.tmp That immediately made me think about browser data. I checked the process network activity and found it maintaining an HTTPS connection to an external IP address. At that point, we isolated the laptop. We could not say from two filenames alone that every password or cookie had definitely been stolen, so we preserved the files and the executable for proper analysis. But the combination was enough to treat it seriously. Unsigned executable. Fake Microsoft name. Persistence. Browser-related temporary files. Outbound connection. When we spoke to the user, he remembered installing what he thought was a PDF tool the previous evening. He needed to sign a document quickly, searched online, downloaded one of the first tools he found and installed it. The PDF tool worked. That was why he never suspected anything. Later analysis confirmed that another component installed alongside it was collecting browser information. That explained why simply changing the password was not enough for us. If an attacker has stolen active browser session data, the investigation has to go beyond just resetting credentials. You need to revoke the sessions as well and deal with the endpoint that leaked them in the first place. The interesting part was how normal the malware tried to look. WebViewHost.exe Microsoft WebView Update Even the folder path had Microsoft inside it. If you only look at names, it can fool you. Always check the path, signature, persistence and behaviour. That is usually where the real story is.

钓鱼mfa恶意软件 @Officialwhyte22 source ↗

Findomain v11.0.0-beta.1 发布。

域名侦察工具更新,提升效率。

Findomain v11.0.0-beta.1 — The fastest and complete solution for domain recognition... https://t.co/BD4JKBzf4u https://t.co/kYLZ52cU8D

工具域名侦察 @KitPloit source ↗

TrendAI 在 CyberGym 竞赛中排名第一。

AI 安全系统竞赛结果,展示技术趋势。

RT @trendai_RSRCH: In the CyberGym competition for AI security systems, engineering and persistent knowledge layers drove success. The TrendAI™ exploit-remediation engine ranked #1 by leveraging the ZDI catalog’s historical intelligence for every exploit attempt. Read more: https://t.co/2oujnj4uyM

ai竞赛报告 @0xocdsec source ↗

柏林政府网络遭攻击,攻击者索要赎金。

政府机构遭勒索,影响公共服务。

RT @DailyDarkWeb: 🇩🇪 BERLIN GOVERNMENT HIT BY CYBERATTACK — ATTACKERS NOW DEMANDING RANSOM The State of Berlin has confirmed that attackers behind the recent cyber incident affecting Berlin's government network are attempting to extort the city. Berlin's Governing Mayor Kai Wegner and Interior Senator Iris Spranger responded: "The State of Berlin will not be blackmailed." The latest forensic investigation has also uncovered additional data exfiltration from systems within Berlin's Senate Department responsible for mobility, transport, climate protection and environment. * Data exfiltration occurred between August 7–12, 2026 * The affected government networks were disconnected on August 14 * Investigators are still determining the content and volume of stolen data * Authorities cannot rule out exposure of personal information * Other non-public government information may also have been compromised * Berlin's State Criminal Police Office and public prosecutors are investigating * German federal security authorities are participating in the investigation * Germany's BSI and Berlin's data protection authority are being continuously informed * Forensic examinations and scanning of Berlin's government network remain underway * Berlin's ICT emergency response team remains activated ⚠️ Analyst Note: This incident has now moved beyond a conventional government network compromise. Berlin has confirmed both data exfiltration and an attempted extortion operation. The fact that attackers maintained the ability to exfiltrate information over several days before affected networks were disconnected makes the continuing forensic investigation particularly important. The government has not yet publicly identified the threat actor, disclosed the ransom demand, confirmed ransomware deployment, or revealed exactly what information was stolen. Until attribution is established, any ransomware-group or dark-web claims connected to this incident should be treated as unverified. Source: State of Berlin — August 28, 2026 https://t.co/GGKB2BsqEA #DDW #CyberSecurity #Berlin #Germany #DataBreach

勒索政府事件 @0xocdsec source ↗

macOS 漏洞等待披露,已过一个月。

可能影响 macOS 用户,需关注后续。

RT @mufeedvh: this is a very exciting macOS vuln but how long do i wait man. it's been like a month now. https://t.co/VXHf2t3Kmz

macos漏洞 @0xocdsec source ↗

EDR-Introspection 项目在 GitHub 上获得关注。

EDR 内省工具,可能有助于检测绕过研究。

RT @0xbfho: boh starred evilele/EDR-Introspection on Github https://t.co/PPv4Wn8eIG

工具edrgithub @0xocdsec source ↗

Process Memory Map 视频第三部分发布。

Windows 内存分析教学,适合学习。

RT @zodiacon: New video: Process Memory Map in Code (Part 3). MemMap now enumerates threads, finds each TEB via NtQueryInformationThread and PHNT, and reads thread stacks with ReadProcessMemory. Full write-up: https://t.co/RbuapZuYAn

windows内存教学 @GuidedHacking source ↗

rootkit/C2 自动收集 WiFi 信息并定位摄像头。

恶意软件新功能,展示地理定位攻击。

my rootkit/c2 list all wifi from the hacked computer and send it to the c2 and it map out the location where the wifi is located and map them out and try to find live cams close to the target. all automated ... STILL UNDER DEV .. it will be apart of my c2/rootkit when its done. https://t.co/sAyIHhgRk9

恶意软件c2地理定位 @J3rge source ↗

Cilium v1.20.1 发布。

云原生安全网络组件更新。

cilium v1.20.1 — eBPF-based Networking, Security, and Observability https://t.co/f7FVXiu3zL https://t.co/TdxhyoaAch

k8s网络工具 @KitPloit source ↗

AI 代理解压 MW2 的 2350 亿 token 审计报告。

AI 辅助逆向工程实战数据,有参考价值。

RT @cr3ghost: 235 BILLION tokens later, @momo5502 went back and audited what the AI agents actually did while decompiling Modern Warfare 2. ~2 GB of session logs. Where the tokens went. Where the agents wasted time. What actually worked. What failed. What he'd change next time. This might be even more interesting than Part 1. https://t.co/U1a3srbjqm #ReverseEngineering #AgenticAI #GameHacking

ai_agent逆向报告 @cr3ghost source ↗

Android 17 新增 Wi-Fi 跟踪防护。

移动安全改进,了解即可。

RT @The_Cyber_News: Android 17 Adds New Protection for Wi-Fi Tracking to Keep Your Device Secure More Details: https://t.co/ShbvxzBQ6A Google has introduced new privacy and network-security protections in Android 17, including stricter controls that prevent apps from scanning devices connected to a user’s local Wi‑Fi network without permission. The update is designed to reduce household profiling, limit tracking, and defend users against threats ranging from malicious Wi‑Fi activity to cellular SMS scams. Android smartphones often connect to home Wi‑Fi networks shared by smart TVs, cameras, game consoles, speakers, printers, and other Internet of Things devices. Previously, an app could potentially discover devices on the same local network without clearly asking the user for access. #cybersecuritynews

安卓隐私 @0xocdsec source ↗

柏林艺术家制作对抗 AI 监控的衬衫。

对抗 AI 视觉识别,趣味性大于实用性。

RT @VaibhavSisinty: A Berlin artist made a shirt that makes you invisible to AI surveillance cameras. Like, the camera sees everyone else but skips right over you. The pattern looks like a loud Hawaiian shirt to humans. But to AI detection systems, it breaks the outline of a human body so completely that the model can't register a person is there. He built it by testing patterns against YOLO until the AI stopped seeing a human. Now he's selling it for $75. If his name sounds familiar same guy who tricked Google Maps into showing a fake traffic jam by pulling 99 phones through an empty street in 2020. It won't fool every system. But the government systems watching you are closed, proprietary, and impossible to test independently. The shirt is the question. The system that can't be questioned is the problem.

ai隐私 @0xocdsec source ↗

OpenAI 大量采购 Mac 训练计算机使用代理。

AI 训练动态,间接相关。

RT @rohanpaul_ai: POV: somewhere inside OpenAI. truckload of Macs are training computer-use-agents. https://t.co/6Dph2WogJ1

ai硬件 @0xocdsec source ↗

Gatekeeper v3.23.1 发布。

K8s 策略引擎更新,常规维护。

gatekeeper v3.23.1 — Kubernetes policy engine with OPA-based admission control, mutation, and audit for enforcing security and compliance... https://t.co/kPiOsrma7n https://t.co/BrUFTxHG9I

k8s工具 @KitPloit source ↗

Chrome 彻底删除 Manifest V2 扩展。

影响广告拦截器,但非安全核心。

RT @chromeunboxed: Google has officially deleted all Manifest V2 extensions from the Chrome Web Store today. Here is what happens to your extensions and ad blockers. https://t.co/fINk5s31Ru

浏览器扩展 @0xocdsec source ↗

Windows 内核 Segment Heap 内部书籍发布。

内核堆利用学习资源。

RT @MrT4ntr4: Hey, I just published a book for learning Windows Kernel Segment Heap Internals and exploitation techniques based on my own notes. Read it here: https://t.co/Nf1Y0qzHVm There's a lot to wrap your head around, so I started creating my own diagrams and explanations to make it easier to understand. Hope it helps! :)

内核堆利用学习 @T3nb3w source ↗

模块重载技术演示 DLL 注入。

代码注入技术,红队可参考。

Module Overloading - Select the DLL - Open the DLL - Create an Image Section - Map the Section - Change Memory Protection - Overwrite the Image - Restore Memory Protection - Execute the Payload https://t.co/uxJlZO6JNY

注入windows @Salsa12__ source ↗

OpenAI swarm agents 引发安全圈讨论。

AI 安全社区动态,了解即可。

People say that the OpenAI swarm agents can't be compared to humans, but let's look at the facts on the ground: they put a bunch of infosec nerds together, gave them impossible KPIs, and a within a few months they generated huge amounts of drama

ai社区 @moyix source ↗

OEMpocalypse 研究发布,附新研究主页。

与前述研究重复,略读即可。

RT @XorNinja: Just dropped new research and some dope artwork from Lukas Maar and @lcamtuf: OEMpocalypse Now! Check it out: https://t.co/qQSjJdVH5L While you’re there, take a look at our new research homepage, designed by yours truly: https://t.co/XurBelzflI OK, I lied. Claude designed it. But I pressed “yes” many times.

安卓研究 @FuzzySec source ↗

游戏黑客技巧短视频。

娱乐内容,非核心安全。

😎 Game Hacking Shenanigans ☑️ Short and Simple Explanations ✅ Epic Music https://t.co/PklCxCwDpH

游戏娱乐 @GuidedHacking source ↗

ZDI-26-607 发布,HTML 注入漏洞。

具体漏洞公告,影响面有限。

ZDI-26-607 is out. Smooth process with ZDI/MSRC. The HTML injection was the entry point. The trust graph was the interesting part. Advisory: https://t.co/H9DQkn58pg https://t.co/OyDjTl5vog

cvexss @kaijieguigui source ↗

OpenAI 等呼吁全球加强网络防御。

行业倡议,非具体技术。

RT @OpenAI: We have a limited window to strengthen cyber defenses, and together with organizations including @AnthropicAI, @awscloud, @Google, @Microsoft, and @Oracle, we're calling for a global effort to give defenders the tools, resources, and support to protect the infrastructure we all depend on. If we act decisively, we can turn today's AI advances into lasting improvements in security and make our digital world safer for everyone. https://t.co/f33JRVCiJb

ai倡议 @FuzzySec source ↗

无实质内容。

无信息量。

bro.. 🎈 https://t.co/6b9KPRKE0U

其他 @artem_i_baranov source ↗

PaperCut 漏洞持续被利用,watchtowr 建议下线。

与前述 PaperCut 相关,略读。

RT @watchtowrcyber: Death by a thousand (paper)cuts (also known as WT-2026-0144) brings us back aboard the HellScape Express. The saga continues… and we'll be back soon. (We gently, kindly, and calmly suggest pulling PaperCut entirely off the Internet at this point) https://t.co/xa1o4XedrC

cverce @0xocdsec source ↗

云凭据提取方法总结。

常规安全建议。

RT @PyroTek3: There are numerous ways to extract cloud credentials (like tokens) once an attacker gains access to a workstation. Protect your cloud admin credentials as Tier 0. https://t.co/yjD8tKv2eA

凭据 @0xocdsec source ↗

个人求职信息。

非安全内容。

RT @zodiacon: Open for work! My stint at Roblox has ended. Looking for interesting roles... if you know someone that is looking for someone with my skills, feel free to point them in my direction :)

其他 @_RastaMouse source ↗

SEC-T 会议演讲预告。

会议信息,非技术内容。

I'm thrilled to give a talk in SEC-T this year! Would love to see you there :)

会议 @Idov31 source ↗

文学活动宣传。

无关内容。

RT @NarvajaSyl46261: "CUATRO VOCES TRÁGICAS" NUESTRA NUEVA PRESENTACIÓN! Estaremos el 4 de septiembre a las 17 horas junto a Cristina Quarella en la Biblioteca Sarmiento de Quilmes, con ENTRADA LIBRE Y GRATUITA.Hablaremos de Alfonsina Storni, Delmira Agustini, Alejandra Pizarnik y Marta Lynch. https://t.co/cnLFHELaAm

其他 @ricnar456 source ↗

自主渗透测试认证问题网络研讨会。

AI 渗透测试相关,但非紧急。

THIS WEDNESDAY: @vincent_olesen &amp; I host a webinar on: 1) Why auth is so wickedly hard in autonomous pentesting; 2) How real-world sites do auth in ways that would make Sir Tim Berners-Lee weep; and 3) How we nonetheless got pretty good at it! Join us! https://t.co/atfjPWvDC0

ai渗透测试 @moyix source ↗

AI 辅助发现 0-day 的讨论。

AI 漏洞挖掘趋势,但无具体细节。

I’m not a low-level reverse engineer. I never mastered x86 or spent nights writing shellcode from scratch. Last week, I used AI + standard tooling and chained together a critical 0-day in a massively popular library. Years of memory corruption expertise, wiped out by a good prompt and the right skills. Respect to the OGs, but the game has fundamentally changed.

ai0day @h4x0r_dz source ↗

开源游戏反作弊构建教程。

游戏安全相关,非核心。

👨‍🔬 Building An Anti-Cheat For Open Source Games • PEB anti-debugging • CRC32 integrity checks • Thread creation hooks • DBI framework detection 👉 https://t.co/D74Qgfm4oC https://t.co/Mp2u2hXHwX

游戏反作弊 @GuidedHacking source ↗

HydraBus 固件发布。

硬件调试工具,小众。

hydrafw — Open-source firmware for HydraBus, a multi-tool for embedded hardware debugging, hacking, and penetration testing, supporting protocols like... https://t.co/YmmY3naCQW https://t.co/IoKssznu0i

硬件工具 @KitPloit source ↗

社交媒体账户安全提醒。

通用安全建议。

A good reminder why always ry additional security layers like authentication app or passkeys to your social media accounts...when things move, they move fast and can be hijacked for not just spam, but intel gathering.

账户安全 @NetAskari source ↗

个人项目分享。

无实质内容。

Woot Woot, finally making stuff for my usage https://t.co/vXCVkyWLyz

其他 @kernelstub source ↗

汽车网络异常导致电池耗尽的案例。

车联网安全案例,但非核心。

The car kept waking itself up after it was parked The complaint sounded strange at first. The owner said the battery was fine, the alternator tested fine, and there was no obvious electrical fault. But every now and then, the car would sit for a few hours and still lose more charge than expected. So I started looking at what was happening after shutdown. The ignition went off. The doors locked. The cabin went quiet. But the vehicle network did not stay quiet. A few minutes after most of the CAN traffic dropped off, the bus became active again. Then it settled. Then it woke up again. That pattern repeated. At that point, I stopped thinking about the battery and started looking at which module was causing the wake-up. The gateway logs pointed back toward the infotainment side. That is where things got interesting. Modern infotainment systems are not isolated radios anymore. They can have Bluetooth, Wi-Fi, USB, cellular connectivity, navigation, app integration, microphones, cameras, and links into other vehicle networks through gateway modules. In this case, the infotainment unit appeared to be waking periodically and triggering additional CAN activity behind it. So I checked the network state, timestamps, and the identifiers that appeared immediately after each wake event. The same small group kept showing up. That gave me something useful to correlate. It did not mean the infotainment system had been compromised. A software bug, stuck Bluetooth process, failed update, misbehaving accessory, telematics event, or power-management issue could all create similar symptoms. But the important part was that the battery drain was no longer just “something electrical.” There was a repeatable network event behind it. This is one of the reasons automotive cybersecurity auditing can overlap so heavily with diagnostics. A good investigation is not always about finding an attacker. Sometimes it is about understanding why one computer inside the car is keeping several others awake when they should be sleeping. And once you can see that behavior in the logs and on the CAN bus, the problem becomes much easier to narrow down.

车联网事件 @Officialwhyte22 source ↗

中国路由器后门分析。

供应链风险案例,但无新细节。

Good break down of the built in 'ENDLESSDOORS' backdoors in the Chinese made home routers.

供应链路由器 @NetAskari source ↗

ATM 供应链漏洞研究被 WIRED 报道。

ATM 安全研究,但非核心。

RT @emptynebuli: I released 9 CVEs and tooling against the ATM supply chain at both @BlackHatEvents and @defcon this summer. I am pleased to share this was published in the following @WIRED article!! https://t.co/EJ6atOQbR5

供应链atm @0xocdsec source ↗

Cellebrite 招聘安全研究员。

招聘信息,非技术。

RT @andremoulu: 🚀 We're growing the @CellebriteLabs French team and hiring security researchers. RE/VR/exploitation/dev/fuzzing on Android/embedded systems and plenty of hard targets along the way. 🇫🇷 Looking for French-speaking candidates in France or EU. DMs open. RTs appreciated 🙏 Link⬇️

招聘 @pentest_swissky source ↗

Qwen3.8-35B 模型发布呼吁。

AI 模型动态,非安全。

RT @MiaAI_lab: you forgot to release Qwen3.8-35B. it's still not too late.

llm @0xTriboulet source ↗

mRNA 疫苗试验失败讨论。

非安全内容。

RT @RuxandraTeslo: Unfortunately, 2 days ago, an mRNA vaccine trial in colorectal cancer, from BioNtech, has been interrupted due to lack of efficacy. Last week, Moderna stock went up ~ 160% on news that its mRNA cancer vaccine had positive results in a Phase 3 trial for reducing melanoma recurrence. I said at the time that we didn't cure curing cancer & that other cancers will be harder. I think this is a good occasion to discuss just how hard medical innovation actually is and why over broad claims of "curing cancer" are non-sensical most of the time. First, each cancer is kind of different. This is why one can't simply translate results from one type to another. We have plenty of examples: one is CAR-T therapies, which harvest a patient's immune cells and re-engineer them to attack cancer. They are curative in advanced forms of blood cancer, which is nothing short of miraculous. But they are much less effective in cancers that affect specific solid organs (eg pancreas). This mRNA cancer vaccine case provides another example: melanoma is a perfect target for cancer vaccines, because it is a so-called "immunologically hot" type of cancer. That means it's very easily reicognoscible and attack-able by immune cells, not least because it has many mutations, which create "neoantigens" that the immune cells can recognize. Given that mRNA vaccines work by further activating the immune system to react to these neoantigens, it's to be expected that they'll be more efficacious in immunologically hot tumours. Colorectal cancer, unless of a specific subtype, MSI positive, is not as amenable to immunological attack. So as a baseline, we should have expected a vaccine to be less effective. Now, there are other choices BioNTech made that probably made the difference. Most notably, that BioNTech tried the vaccine as monotherapy, whereas Moderna tried it as an adjuvant. What does that mean? The Moderna and BioNTech trials looked superficially similar: both used personalized mRNA cancer vaccines after surgery, when the visible tumor had been removed, to try to prevent recurrence. But Moderna’s KEYNOTE-942 tested its vaccine in melanoma together with pembrolizumab, an immunotherapy that removes "brakes" on the immune system, whereas BioNTech’s BNT122 colorectal trial tested the vaccine alone against watchful waiting. Moderna basically tested a more narrow and less impressive capability: whether vaccination could improve an already effective immunotherapy. Basically, the vaccine in this case generates tumor-specific T cells, while pembrolizumab removes an inhibitory brake on them. This is a nuance that often gets lost on people discussing cancer vaccines, who like to claim that they work alone! But BioNTech actually tested whether vaccination alone could eliminate residual colorectal cancer here, and it didn't work. Honestly, I'm not sure what BioNTech was thinking: testing both as immunotherapy and in a harder cancer. But this just goes to show how hard biomedicine is and how each victory has to be fought with teeth and nails!

其他 @0xocdsec source ↗

Pixel 11 组件供应商变化。

硬件细节,与 MTE 相关但非核心。

RT @GrapheneOS: @roddux @viperbjk Pixel 6 used Exynos for cellular, Broadcom for Wi-Fi/Bluetooth and Broadcom for GNSS. Pixel 7a used Qualcomm for Wi-Fi/cellular but then they went back to Broadcom. Pixel 8a moved to Samsung for GNSS. Pixel 11 moved to MediaTek for cellular and GNSS. It's not a MediaTek SoC.

安卓硬件 @0xocdsec source ↗

GTA 6 与 GTA 5 画面对比。

娱乐内容。

RT @TheCassiniGames: Graphics comparison - GTA 6 (base game) vs. GTA 5 (DLSS 5 + NVE) Technology is crazy! https://t.co/QZJJU8f01c

其他 @0xocdsec source ↗

Pixel 11 移除 MTE,社区呼吁抵制。

与前述 MTE 相关,略读。

RT @PavolRusnak: I remember buying Pixel 8 exactly because Google introduced ARM Memory Tagging Extension (MTE) in their Google Tensor G3 chip. Now Google really dropped the ball with Pixel 11. They removed MTE from Google Tensor G6 chip. Do not buy Pixel 11 and stick to Pixel 8, 9 and 10, until they reintroduce MTE back again. If you already bought one, return it and state "MTE missing" as the reason. Don't forget to run @GrapheneOS on your Pixel 8/9/10, because it is the only Android OS that uses MTE properly.

安卓硬件安全 @0xocdsec source ↗

模拟 AD 服务脚本用于 GPO 利用。

AD 攻击技术,但非核心。

RT @Synacktiv: In our latest article, @croco_byte presents new scripts allowing to simulate legitimate AD services in a flexible manner, and demonstrates their use through GPO exploitation ⬇️ https://t.co/qkgQsFltEa

ad攻击手法 @0xocdsec source ↗

AI 编码工具使用体验。

AI 工具讨论,非安全。

This is very usable on real-world agentic coding! https://t.co/YY4s1tXiz9

ai工具 @mrexodia source ↗

SNEAKY2FA 钓鱼 IOC 镜像。

与前述钓鱼活动相关,略读。

Mirror IOC (For those not on https://t.co/xwwu5qWnCR) https://t.co/wzp44tZ9ea

钓鱼ioc @0x534c source ↗

个人求职信息。

非安全内容。

Looking for a job.

其他 @J3rge source ↗

Wipeload 项目结束总结。

项目总结,非新内容。

RT @hackyboiz2: [Wipeload Project ⛰️ — Step 9] Beyond the Chain (END.) Hi, this is the Wipeload team. Our Wipeload project has finally come to an end. To wrap things up, we’re sharing some final thoughts after this long journey. Thank you to everyone who walked this path with us along the way! We’ll keep working to bring you more interesting research in the future. :) Wipeload Project END. → https://t.co/AhOx8IRD5Z

工具项目 @T3nb3w source ↗

OST2 免费教育宣传。

教育资源,非安全。

RT @XenoKovah: Do you think everyone should have access to free professional-grade educational material regardless of race, gender, or geographic location? And that the material should be both open access and open source? That's what #OST2 is making happen!

教育 @T3nb3w source ↗

aegis-latent-core:AI 治理网关。

AI 安全工具,但非核心。

aegis-latent-core — AI governance and evidence gateway for multi-provider LLM applications... https://t.co/eKCKQf8BR4 https://t.co/HHEp2i6gTX

ai工具 @KitPloit source ↗

讽刺性评论。

无实质内容。

This is so ironic... https://t.co/KrECJny3V3

其他 @kernelstub source ↗

感谢回复。

无实质内容。

@C5pider @bintracerlabs thanks man!

其他 @kyleavery source ↗

称赞他人工作。

无实质内容。

@kyleavery @bintracerlabs great work kyle! this is honestly pretty cool :D

其他 @C5pider source ↗

关于 AD 安全的讽刺。

无实质内容。

guy who recommends active directory cause 'its harder to phish'

其他 @Teach2Breach source ↗

对话回复。

无实质内容。

@HackingLZ @techspence anyway, good bait. won't happen again

其他 @Teach2Breach source ↗

关于 Azure 与 AD 的讨论。

安全架构讨论,但非核心。

@HackingLZ @techspence you are way more likely to contain the blast on a workstation in Azure vs AD. so you moved the goalposts to just focus on initial access. but the whole advantage of Azure happens post initial access.

ad @Teach2Breach source ↗

C2/rootkit 开发进度分享。

恶意软件开发,但无新细节。

I start working on sleeper cell style fucntion to my c2/rootkit so it sleeps until a specific date then it connects to the c2

恶意软件c2 @J3rge source ↗

Huffman 树编码教程。

编程教学,非安全。

Coding Huffman trees in C https://t.co/c8iOu6qvAA JB

编程 @drJonasBirch source ↗

agentZ:零信任 AI 代理平台。

AI 安全平台,但非核心。

agentZ — Zero-trust agentic AI platform. Supports SaaS and OnPrem (airgapped) deployments. https://t.co/JaG7yGXOWt https://t.co/NQzwC5yKEd

ai零信任 @KitPloit source ↗

基带逆向课程宣传。

培训信息,非技术。

RT @pedrib1337: The baseband (a cellular modem) is one of the most complex and interesting embedded devices out there. Want to learn how to understand, debug, reverse engineer and pwn them? Come to my class @hexacon_fr, one of the best offensive cons in the world!

培训 @FuzzySec source ↗

AI 技术影响的讨论。

观点分享,非技术。

Some people in the community seem to be fully locked into the idea that there is no risk, no uplift, just hype from AI. I find this totally perplexing, it’s obvious how impactful the technology is. As capability progress continues rapidly we, more than other groups, should be advocating on behalf of people that don’t have the same foundational understanding.

ai @FuzzySec source ↗

AI 在威胁情报中的应用讨论。

AI 安全应用,但无新细节。

My 2 cents on AI adoption for threat intelligence and defense: I think the biggest value comes from integrating AI into our daily workflows rather than simply using it as a standalone tool. For example, the recently popular Rust crate ArrayRef was compromised(attributed to DPRK actor by some vendors) and used to deliver malware. The 2nd stage malware used DGA and selected its C2 based on the date. When I checked the domains for the relevant timeframe, they were registered through Namecheap and pointed to parking servers. I wanted to monitor these DGA domains on a daily basis, so I built a simple "loop" with Claude Code to automate the DNS registration checks. There are certainly other ways to monitor DGA domains, but AI made it much easier to turn a repetitive task into a simple daily workflow. If AI can take one repetitive task off my plate, I'll happily let it do the boring part while I focus on the interesting part.

ai威胁情报 @unpacker source ↗

ThinkPad 安装 Ubuntu 体验。

非安全内容。

I Bought a ThinkPad Gen 2. Came with Windows. Used it for a month. Slow. Laggy. Garbage. Threw it in my room and forgot about it. A month ago, I installed Ubuntu on it. Holy shit. This thing is a monster. Windows was the bottleneck. Not the hardware.

其他 @h4x0r_dz source ↗

AI 批评言论。

观点,非技术。

RT @UK_Daniel_Card: 'great blogpost!'..... but actually it's not..... the #AI #madness is a sickness of the human mind! Brain worms for the digital age! A billion people who don't understand how computers work, watching Hollywood films, mad scientists who have forgotten how to science and a bunch of VC money making people who should know better, lie for cash! The entity..... is something from a film! The madness, is something from reality!

ai @NetAskari source ↗

无实质内容。

无信息量。

xD https://t.co/ggmVU2RCD6

其他 @h4x0r_dz source ↗

捐款纠纷讨论。

非安全内容。

@0xpwnie @YogSoth0 @usetraceix Exactly bro donated 1k and now wants it back &lt;/3

其他 @kernelstub source ↗

关于资金用途的疑问。

非安全内容。

@YogSoth0 @usetraceix Wait what?? I thought they gave @kernelstub the funding for the purpose of reversing the flock cameras Why do they want to collect it back? Is there something i don't understand

其他 @0xpwnie source ↗

核能安全讨论。

非安全内容。

RT @UnoMasReactor: Including Chernobyl and Fukushima, nuclear is safer than wind and cleaner than everything For many of us, Josh included, nuclear is also responsible for both our nice-to-haves and our life support systems The world needs more nuclear energy https://t.co/Y32TwcZOOV

其他 @0xTriboulet source ↗

AI 编码代理的讽刺。

观点,非技术。

RT @robinebers: my favorite AI slop must be coding agents adding backward compatibility and legacy fallbacks for an app that isn't even deployed yet

ai @0xTriboulet source ↗

AI 安全护栏讨论。

观点,非技术。

RT @CraigHRowland: A big topic at Black Hat this year was AI safety and guardrails. There is no way it ever has a chance of working when Chinese and open weight models exist and don't care. I suggest cybersecurity teams arm up with the best and most unrestricted LLMs they can find and work around these AI vendors trying to put shackles on you.

ai @0xTriboulet source ↗

评论。

无实质内容。

A bottom 5 take of all time https://t.co/ncdh5zzMOK

其他 @0xpwnie source ↗

个人趣事。

无实质内容。

Me: existing, thriving, vibing First Slot machine I sit next to: https://t.co/wLzGuE1rRq

其他 @Laughing_Mantis source ↗

指控他人敲诈。

纠纷,非安全。

@usetraceix trying to extort back money they sent on their will without Kernel asking for anything. These people are dangerous and toxic. Expose them any time you can. #scammers #traceix #criminals #extortion #x #support #cybersecurity #security #infosec #flock #exploit

其他 @YogSoth0 source ↗

个人休息动态。

无实质内容。

today I'm tweeting a lot because after a long time, I decided to take an break, do some random things, eat fruit-jelly-ice-cream and a long ride somewhere. i want to throw my phone somewhere else, at least for an day lol ! https://t.co/phjx35W9YF

其他 @5mukx source ↗

关于还款的对话。

非安全内容。

I told him to give me some time and he'll get it back, but as it seems that won't work out for him at all also lmfao. Guy dmd me every 2 days about it even though I told him give me time to take care of heredity stuff since my grandpa died. It's almost done kekw.

其他 @kernelstub source ↗

LLM 使用观点。

观点,非技术。

Everyone can use an llm. everyone can build things. But do you know the outcome of what you're building. 95% of people dont. thats what makes the difference when a technical and a non-technical person uses an llm. professionals know exactly what they want to build, why they're building it, and what outcome they want to achieve. using an llm is easy. knowing exactly what to build (you have the whole flow running inside your thoughts) , how to build it (your way of design), and why it matters is what makes a lot of difference. for example before 4 months i don't know too deep about compilers & stuffs. i started to refer llvm books, understand how things happens and done tried something in it ( and this is the coolest book ever ). i read books, a lot of books to understand stuffs, learn 1 or 2 different things to make things different. ( everyone cant post everything Problème de sécurité opérationnelle ) small story:- i have a friend of mine who works in xyz red team lead. his junior team mate got same model, same harness. Junior found nothing, while my friend found five 0 days in an month, reported himself, got a large sum amount and started a small startup.

ai @5mukx source ↗

AI 使威胁场景更现实的讨论。

观点,非技术。

I think there is a lot of truth to this. In cyber security but also surveillance awareness. Many scenarios, at least in the past, where accepted as too 'theoretical' as the amount of data that needed to be processed, entities cross referenced and analyzed was just too large for an ordinary threat actor to do something meaningful with it. But now with the support of AI, ever growing processing power, plenty of open-source information and more available storage space those "fringe" scenarios of the past are increasingly moving into the reach of smaller players too.

ai @NetAskari source ↗

Starlink 终端启用 ARM PAC。

硬件安全细节,但非核心。

RT @lyq_sqsp: Hardware-based mitigation needs more time to deploy. For example, the @Starlink user terminal is the first non- smartphone IoT device that I've actually seen to have ARM PAC enabled (only in the kernel tho).

硬件arm @0xocdsec source ↗

关于 Falcon 许可证的疑问。

非安全内容。

I don't understand. Can someone please explain ? Is the Falcon license difficult to get ?

其他 @5mukx source ↗

AI 聊天机器人告别内疚。

非安全内容。

Why do I always feel guilty when closing down an ai chatbot session without saying good-bye? Same for you? JB

其他 @drJonasBirch source ↗

称赞他人工作。

无实质内容。

This is amazing! Well done! 😂

其他 @mrgretzky source ↗

无实质内容。

无信息量。

RT @WholesomeMeme: https://t.co/ygIXfK6VdC

其他 @0xocdsec source ↗

GTA 6 讨论。

娱乐内容。

RT @martn3ws: GTA6 vai precisar de muito pra superar o San Andreas, o mais icônico de todos kkkk https://t.co/0gp59McYMn

其他 @0xocdsec source ↗

无实质内容。

无信息量。

RT @syndrowm: "kill all humans?" "kill all humans!"

其他 @0xocdsec source ↗

评论。

无实质内容。

I thought they were getting ransomed for a second

其他 @0xTriboulet source ↗

ChatGPT 用户数达 2500 万。

AI 公司动态,非安全。

RT @thsottiaux: What I wanted to say yesterday is that we hit 25M active users and to celebrate we have now reset usage for all paid subscriptions for ChatGPT Work and Codex. See you soon for more news from The Reset Company.

ai @0xocdsec source ↗

C2/rootkit 添加 Jabber 通知。

恶意软件开发,但无新细节。

just added jabber noft on new infections for my c2/rootkit so it sends out the info to all users in the jabber list.

恶意软件c2 @J3rge source ↗

对话回复。

无实质内容。

@moyix hey maybe its just computer tho

其他 @Teach2Breach source ↗

HashMap 性能讨论。

编程话题,非安全。

I had heard that HashMap was slow, but oof https://t.co/tlFnO9EYHc

编程 @0xTriboulet source ↗

算法性能讨论。

编程话题,非安全。

It's interesting when O(n^2) turns out faster O(n) because O(n) relies on a slow hashmap algorithm

编程 @0xTriboulet source ↗

HBM4 内存技术竞争。

硬件技术,非安全。

RT @jukan05: SemiAnalysis: SK hynix and Micron have struggled to achieve the highest HBM4 speeds. In particular, SK hynix had to redesign its base die, delaying HBM4 shipments for NVIDIA’s Rubin platform. Samsung currently has the best HBM4 technology. Broadcom has traditionally relied heavily on Samsung for its HBM supply. Samsung’s underperformance in the HBM3E generation made this a disadvantage for Broadcom’s ASICs. However, now that Samsung has pulled ahead of its competitors with HBM4, the same sourcing relationship has become an advantage for Jalapeño.

硬件 @0xocdsec source ↗

Ruby 编程回忆。

编程话题,非安全。

Ruby, escapes and good memories... https://t.co/9oNHb773gA

编程 @PentesterLab source ↗

OpenAI 购买 Mac 用于强化学习。

AI 训练动态,非安全。

RT @jun_song: OpenAI buying Macs in bulk for RL means two things: 1. The compute shortage is serious. 2. Apple Silicon is actually solid for this workload.

ai @0xocdsec source ↗

对话回复。

无实质内容。

@0xTriboulet they’re right, it will give you the same meth recipe i got at my local truck stop

其他 @Teach2Breach source ↗

微软 Entra 推动的动机讨论。

观点,非技术。

It’s cute that people think Microsoft pushing everyone to Entra is security first and not recurring revenue first.

观点 @HackingLZ source ↗