Loading story…
Academics from Vrije Universiteit Amsterdam have developed 'L1TF Reloaded,' an attack that chains L1 Terminal Fault (Foreshadow) and a Spectre variant to bypass existing CPU mitigations in public cloud environments. The attack enabled data leakage across virtual machines on Google Cloud, including the extraction of an Nginx TLS key in 14 hours. The findings highlight the need for stronger isolation measures beyond current mitigations.
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
1 event from the most recent confirmed update back to the earliest known activity.
A new attack targeting cloud CPU environments was publicly exposed by security researchers. The disclosure appears in reporting published on September 23, 2025, with no earlier event date provided in the reference.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Researchers from Vrije Universiteit Amsterdam developed 'L1TF Reloaded,' a novel attack combining L1TF (Foreshadow) and half-Spectre, successfully leaking VM memory from Google Cloud despite existing mitigations. The exploit enabled extraction of sensitive data, such as TLS keys, from co-tenant VMs and the hypervisor, even under high-noise conditions. Standard mitigations were insufficient, and only advanced protections like those on AWS limited the impact to non-sensitive data leaks.
Jun 29, 2026
Researchers disclosed the **Meltdown** and **Spectre** hardware flaws, showing that speculative execution in modern processors could let attackers read sensitive data across security boundaries on affected devices. Reuters reported that **Meltdown** primarily affected Intel processors by breaking memory isolation, while **Spectre** impacted Intel, AMD, and ARM chips by tricking applications into leaking secrets such as passwords and other protected data. CERT/CC later summarized the broader issue as cache side-channel attacks against CPU hardware using speculative execution, underscoring that the weakness was architectural rather than limited to a single product line. Major vendors and cloud providers moved to contain the fallout with software, firmware, and microcode mitigations, including Microsoft Azure protections for hosted customers and public advisories from manufacturers such as Huawei. Subsequent research showed the problem persisted beyond the initial disclosures: the **ZombieLoad** attacks demonstrated additional Intel data-leakage paths tied to speculative execution, and a later **TSX Asynchronous Abort (TAA)** variant affected some processors previously thought to be resistant. Intel issued microcode updates, but researchers and vendors warned that mitigations reduced rather than eliminated risk, that exploitation generally required local code execution, and that fully disabling the underlying CPU behavior would carry significant performance costs.
Jun 29, 2026
Researchers from KU Leuven and the University of Birmingham have demonstrated new physical attacks that undermine the security guarantees of trusted execution environments (TEEs) provided by Intel and AMD processors. These TEEs, specifically Intel's Software Guard Extensions (SGX) and AMD's Secure Encrypted Virtualization with Secure Nested Paging (SEV-SNP), are widely used in cloud computing to protect sensitive data and operations from attackers, even those with administrative access to the underlying infrastructure. The attacks, named Battering RAM and Wiretap, exploit vulnerabilities in the deterministic encryption schemes used by both SGX and SEV-SNP. By inserting a low-cost hardware interposer—costing as little as $50—between the CPU and DDR4 memory modules, attackers can observe and manipulate encrypted data in real time. The Battering RAM attack allows adversaries to not only view but also modify encrypted data, enabling the introduction of software backdoors or data corruption within protected enclaves. The Wiretap attack, on the other hand, enables passive decryption of sensitive data without detection. These attacks are particularly concerning for cloud environments, where confidential computing workloads rely on hardware-level memory encryption to secure data from potentially untrusted cloud service providers. The interposer operates transparently during system startup, passing all trust checks, and can later be activated to redirect protected memory addresses to attacker-controlled locations. On Intel platforms, Battering RAM enables arbitrary read and write access to enclave memory, while on AMD systems, it bypasses recent firmware mitigations and allows the introduction of arbitrary backdoors into virtual machines. The attacks highlight fundamental limitations in the current design of hardware-based memory encryption, especially when deterministic encryption is used. All systems using DDR4 memory and relying on these TEEs for confidential computing are potentially vulnerable. The research underscores the need for more robust hardware security mechanisms and may prompt cloud providers and customers to reassess their trust in existing enclave technologies. The findings have significant implications for the security of cloud-hosted applications, including those used by messaging platforms like Signal and WhatsApp, which depend on these protections to safeguard user data. The attacks demonstrate that physical access to cloud hardware, even with minimal resources, can compromise the confidentiality and integrity of sensitive workloads. Both Intel and AMD are expected to review these findings and consider architectural changes or additional mitigations in future hardware generations. The research also raises questions about the adequacy of current cloud security recommendations and the potential for insider threats within data centers. Organizations relying on SGX or SEV-SNP for critical workloads should closely monitor vendor advisories and consider additional layers of defense. The academic community continues to play a vital role in uncovering and publicizing such vulnerabilities, driving improvements in hardware security.
Jun 29, 2026