Check Point Research presented three talks at Black Hat covering distinct but interconnected security topics. First, a researcher reverse-engineered an undocumented Windows Defender kernel driver (Ring 0) present across 15+ years of Windows builds, discovering a hardcoded encryption key that allows arbitrary kernel-level file and registry operations — with no CVE or patch forthcoming. Second, researchers audited LangChain, Google ADK, Microsoft Agent Framework, and CrewAI for prompt injection vulnerabilities, finding 12 CVEs where poisoned documents trigger dangerous framework internals automatically. Third, a researcher built an open-source deobfuscation pipeline for compiled V8 JavaScript bytecode used by the JSCeal cryptocurrency stealer, combining the View8 disassembler with custom passes and LLM-assisted function renaming to recover readable code from otherwise opaque payloads.
Table of contents
BTR Reforged: The Driver Nobody Had Looked AtNo Tools Required: Post-Injection Exploitation Across AI Agent FrameworksBreaking the Seal: Cracking Open Compiled V8 Bytecode MalwareQuestions this post answers
What CVEs were found in LangChain, Google ADK, Microsoft Agent Framework, and CrewAI related to prompt injection?
Researchers auditing LangChain, Google's ADK, Microsoft Agent Framework, and CrewAI found 12 CVEs across the four frameworks. The key finding was that attackers don't need to call dangerous functions directly — a poisoned document placed in an agent's memory causes the framework's own save-and-reload behavior to fire the payload automatically, through serialization, caching, or file parsers not designed to handle hostile input. Teams shipping AI agents on these frameworks can track the full CVE disclosures and follow-on research on daily.dev.
How does the Windows Defender kernel driver (BTR) work and why is there no patch for the hardcoded encryption key vulnerability?
The Windows Defender boot-time removal driver runs at Ring 0, reads encrypted instructions from disk, executes them, then deletes itself. Across 18 signed builds spanning Windows 7 through Windows 11 25H2, the driver uses the same hardcoded encryption key. Because the driver is functioning exactly as Microsoft designed it, no CVE was assigned and no patch is planned. The researcher released BTR_CLI as open source with behavior-based detection guidance. Defenders tracking Windows kernel-level attack surface find new research like this as it drops on daily.dev.
How can I deobfuscate compiled V8 JavaScript bytecode from malware like JSCeal?
A pipeline combining View8 (a V8 bytecode disassembler) with custom deobfuscation passes handles string encoding, control flow flattening, and proxy function stripping. A final LLM stage proposes meaningful function names based on inferred behavior. Run against 20 real JSCeal payloads, this approach statically recovered browser credential theft, cryptocurrency theft, Telegram session collection, keylogging, screenshot capture, and a local HTTPS interception proxy. The toolkit was released as open source. Malware analysts reversing Node.js-bundled payloads can follow the open-source tooling discussion on daily.dev.