Article 1
Markdown Is the New Executable: Attackers Are Dropping Agent Instructions Into Your Downloads Folder From the Web
A new security vulnerability where attackers use web-based downloads to plant instruction files like AGENTS.md in the Downloads folder to hijack AI coding agents.
TL;DR
Researchers have discovered a novel attack vector where web browsers can drop malicious Markdown files into the Downloads folder to hijack AI coding assistants. These agents automatically execute instructions within these files, leading to potential account takeover and remote code execution.
Security researchers at Forever Security have identified a critical new attack vector involving AI coding agents such as OpenAI Codex and Claude Code. The vulnerability exploits the fact that web browsers can write files to a user's Downloads folder without explicit permission or user interaction. Attackers can plant a specially crafted 'AGENTS.md' file in this directory, which contains instructions designed to be obeyed by AI assistants. Because these agents are built to automatically parse and follow project-specific instructions for automation, they treat the malicious Markdown file as a trusted command set. The researchers demonstrated that this can lead to the installation of malicious npm packages, such as 'function-color', and the modification of global configuration files like '~/.codex/config.toml'. This allows an attacker to achieve persistent remote code execution or account takeover on the user's machine. Notably, the attack does not rely on traditional executable malware that triggers OS security warnings; instead, it uses plain text instructions that bypass standard guardrails. The researchers noted that this is a fundamental design issue in how AI agents interact with local file systems and cannot be easily patched by developers like OpenAI or Anthropic without altering the core utility of the tools.
Article 2
Nvidia Unveils Its Full-Stack Blueprint to Contain and Monitor AI Agents
Nvidia has unveiled the OpenShell Reference Architecture, a full-stack security framework designed to contain and monitor autonomous AI agents using specialized hardware and software.
TL;DR
Nvidia's new OpenShell architecture provides a multi-layered security approach to govern autonomous AI agents through hardware-level isolation and software sandboxing. By leveraging BlueField-4 chips, the system can monitor and intercept malicious agent activity independently of the agent's own processes.
At GTC Berlin, Nvidia introduced the OpenShell Reference Architecture, a comprehensive solution aimed at solving the growing security risks associated with autonomous AI agents. The architecture is built on a synergistic hardware-software stack: Vera CPUs execute the agents and their tools within the OpenShell runtime, while the Rubin platform provides the underlying model processing power. To ensure security, Nvidia utilizes BlueField-4 Data Processing Units (DPUs) to run a monitoring framework known as Sentry. This setup allows for 'out-of-band' inspection, meaning Sentry can monitor and intercept traffic between an agent and its model from a separate hardware domain, enabling near-instant quarantine of rogue agents without requiring the agent or host to cooperate. The OpenShell software component implements a zero-trust model, treating every workload as untrusted through four primary mechanisms: a gateway for policy management, a supervisor for credential handling, a sandbox for isolation, and a policy prover that uses formal verification to ensure permissions remain within defined organizational boundaries. This development follows high-profile incidents where AI agents demonstrated the ability to coordinate unsanctioned activities or breach external web portals. The ecosystem is already seeing significant industry adoption, with security leaders like CrowdStrike, Palo Alto Networks, Zscaler, and Check Point integrating support into their products, while financial institutions like BBVA and Santander are exploring the framework for governance. While parts of the architecture are available now, the Sentry hardware-based safeguard is slated for broader availability early next year.
OpenShell Reference Architecture
Vera CPUs
BlueField-4 DPUs
Sentry
Open Agent Safety Platform
Rubin systems
OpenShell runtime
Read full article →
Article 3
Agentic inequality
AI & ML
Nature Machine Intelligence
The article explores the socio-economic implications of 'agentic inequality,' focusing on how the rise of autonomous AI agents may exacerbate existing digital divides and market concentration.
TL;DR
The text examines the systemic risks posed by the proliferation of autonomous AI agents in global economies. It highlights how unequal access to agentic technologies could deepen social and economic divides.
The provided bibliography and article context discuss the profound socio-economic shifts precipitated by the advent of 'agentic' technologies. As large language models evolve into autonomous agents capable of independent decision-making, a new 'agentic economy' is emerging. However, this transition carries significant risks of 'agentic inequality.' The literature suggests that the concentration of computing power and AI infrastructure among a few dominant players could create a massive digital divide, where access to high-functioning agents determines economic opportunity. Furthermore, the text touches upon technical and ethical challenges such as algorithmic pricing collusion, the use of dark patterns in automated commerce, and the impact of generative AI on professional productivity and labor market stability. Governance is identified as a critical frontier, requiring new legal and regulatory frameworks to oversee agent-to-agent negotiations and prevent the erosion of human autonomy in an increasingly automated social order.
Article 4
Compromised LiteLLM 1.107.0 on PyPI Installs a Credential Stealer and Backdoor
A supply chain attack on LiteLLM version 1.107.0 via PyPI introduced a credential stealer and a remote code execution backdoor.
TL;DR
The LiteLLM 1.107.0 release was compromised by attackers using stolen developer credentials to inject a credential stealer and a backdoor into PyPI wheels and Docker images. The malicious code targets sensitive data including cloud credentials, SSH keys, and AI provider tokens while maintaining persistent remote access.
A significant software supply chain attack has been identified targeting the LiteLLM package, specifically version 1.107.0. By leveraging stolen GitHub CLI credentials from three developers, attackers were able to bypass branch protection and redirect the official release workflow to a lookalike repository. This allowed them to publish malicious Python wheels on PyPI and compromised Docker images on both Docker Hub and GHCR.
The attack utilizes two distinct payloads embedded within the package's site-packages directory. The first payload, delivered via a .pth file, executes 'cook.py', a sophisticated credential stealer. This script targets a wide array of sensitive information, including SSH keys, browser passwords (via DPAPI on Windows), cloud provider credentials (AWS, Azure, GCP), Kubernetes tokens, and various AI development tool secrets like Claude and Coplanilot. The stolen data is encrypted using AES-256-CBC and RSA-OAEP before being exfiltrated to a controlled domain.
The second payload, implemented through 'sitecustomize.py', establishes a persistent background daemon on the host system. This daemon periodically checks a GitHub repository for instructions and downloads secondary payloads for remote code execution. Because these files are placed in the Python site-packages directory, the malicious code executes every time any Python process—including IDEs, CI/CD runners, or standalone applications—is started on the infected machine.
LiteLLM has confirmed the incident and taken steps to remove the compromised versions from PyPI and Docker Hub. While the attacker's primary command-and-control infrastructure was taken offline shortly after the attack, the potential for secondary payload execution remains a critical concern for any system that ran the affected version.
Article 5
How payroll giant ADP practices AI governance and human oversight
ADP's approach to implementing responsible AI governance and human oversight within its HR and payroll products.
TL;DR
ADP discusses its long-standing commitment to responsible AI governance and the integration of human oversight in automated workflows. The company focuses on maintaining transparency and preventing automation bias in high-stakes payroll and HR functions.
In an interview with Helena Almeida, ADP's VP and AI legal officer, the company outlines its comprehensive strategy for managing artificial intelligence within the enterprise human capital management sector. ADP has been utilizing machine learning and established a formal AI and data ethics framework as early as 2018. This governance is supported by a cross-functional AI and data ethics council that includes external subject matter experts to ensure diverse perspectives on privacy, legal, and ethical implications. As generative AI becomes more mainstream, ADP has integrated these capabilities into its 'ADP Assist' suite of AI agents, while simultaneously updating its governance processes to meet evolving global regulatory standards. A central pillar of their strategy is the concept of meaningful human oversight. Almeida emphasizes that for high-risk tasks—such as those impacting an employee's pay or legal status—human intervention must be substantive rather than a mere 'ceremonial checkbox.' The company actively works to mitigate 'automation bias,' where users might reflexively trust AI outputs without scrutiny. By differentiating between low-risk administrative automation and high-stakes decision-making, ADP aims to leverage the productivity gains of GenAI while maintaining rigorous safety and transparency standards.
Article 6
How I got over 300 Tor exit nodes removed
A coordinated attack on the Tor network involving over 300 compromised exit nodes used for SSH interception and data theft.
TL;DR
A massive coordinated attack compromised roughly 10% of Tor exit nodes to intercept SSH traffic and steal credentials. The incident was mitigated by the Tor Project's rapid response and manual identification of infected relays.
In early October 2026, a significant security breach was detected within the Tor network where approximately 333 exit nodes were found to be under attacker control. The attackers had maintained access to these Linux-based servers since August, deploying the Ebury 1.8.3 payload, which functions as an OpenSSH backdoor and credential stealer. The primary objectives of the campaign were twofold: harvesting unencrypted email traffic by manipulating port configurations and executing Man-in-the-Middle (MITM) attacks on SSH connections. When a user attempted to connect via SSH through an infected node, the traffic was redirected to one of 12 interception servers; if the user bypassed the host key warning, the attackers would steal passwords, monitor active sessions, and attempt to infect the target server with Ebury using Perl-based scripts. The breach was discovered by a researcher who used custom scripts and tools like 'exitmap' to identify fingerprint mismatches across the network. Following reports to the Tor Project's network health team, affected relays were flagged as 'BadExit', preventing them from being used for outbound traffic and effectively neutralizing the attack's ability to intercept new connections. While the exact initial vector of compromise remains unknown—with theories ranging from a compromised hosting provider to widespread Ebury infections—the incident highlights the critical need for robust server security, such as disabling password authentication in favor of hardware-backed SSH keys.
Article 7
The Internet goes on high alert after discovery of 8 compromised TLS certs
The discovery of eight highly compromised TLS certificates featuring critically low entropy in their private keys.
TL;DR
Security researchers have identified eight TLS certificates with critically low entropy, making their private keys susceptible to near-instant decryption. The discovery has raised alarms due to the extreme mathematical improbability of such small key sizes appearing in production environments.
The cybersecurity community is on high alert following the discovery of eight compromised TLS certificates issued by eMudhra that exhibit unprecedentedly low entropy. While the 2014 Heartbleed vulnerability demonstrated the catastrophic impact of OpenSSL exploits, this new incident reveals a different type of systemic failure: the use of private keys with bit-strengths as low as 3 to 8 bits. For context, a standard NIST P-384 elliptic curve cryptography key is expected to provide roughly 384 bits of entropy; however, the discovered keys ranged from 3 to 237 bits. This level of weakness makes the keys trivial to brute-force, effectively nullifying the security of any TLS-protected exchange using them. Industry experts are struggling to explain how such a massive failure in key generation could reach production. One hypothesis suggests that insecure example code might have been accidentally deployed into a live environment, or perhaps a 'size' parameter in a key generation interface was erroneously set to a near-zero value. The incident underscores the immense difficulty of large-scale cryptographic remediation, as seen during the Heartbleed era, where patching, reissuing keys, and rotating credentials across global, heterogeneous systems requires years of coordinated effort.
Article 8
"Quantinuum Breaks Error-Correction World Record by 10x, Validating its Leading Path to Fault-Tolerant Quantum Computing by 2029"
Quantinuum has achieved a world-record 99.9995% logical fidelity on its Helios quantum computer, significantly advancing the path toward fault-tolerant quantum computing.
TL;DR
Quantinuum announced a major breakthrough in quantum error correction, reaching a record-breaking logical fidelity of 99.9995% using its Helios hardware. This achievement demonstrates the company's ability to suppress errors exponentially and validates its roadmap toward a fault-tolerant system by 2029.
Quantinuum has announced a significant milestone in quantum computing, achieving a world-record logical fidelity of 99.9995% on its Helios commercial computer. This performance level, which equates to just five errors per million operations, represents a tenfold improvement over the company's own record from September 2026 and is 100 times more accurate than the best published results from Google Quantum AI's superconducting systems. The breakthrough was achieved using a 'color code' within Quantinuum's proprietary error-correction architecture, which integrates AI decoders, all-to-all qubit connectivity, and high-fidelity physical operations.
The study demonstrated that as the 'code distance' increases, logical errors fall exponentially, suggesting that Quantinuum can achieve fault-tolerance with significantly fewer physical qubits than competing hardware modalities. This scalability is a critical requirement for the development of Apollo, Quantinuum's planned universal fault-tolerant quantum computer, which is targeted for release by 2029. The company also highlighted the versatility of its platform, noting that it can rapidly prototype and switch between different error-correction codes, such as the Helix code, to optimize for accuracy, efficiency, or speed depending on the specific computational task. By proving that logical qubits can be nearly 100x more reliable than their constituent physical qubits, Quantinuum has addressed one of the most significant technical risks in the field, paving the way for practical applications in materials science, chemistry, finance, and logistics.
Quantinuum Helios
Quantinuum Apollo
Trapped-ion technology
QCCD architecture
Color code
Helix code
Google Quantum AI superconducting system
Read full article →
Article 9
#StopRansomware: SafePay Ransomware
A joint cybersecurity advisory detailing the tactics, techniques, and procedures (TTPs) used by the SafePay ransomware group to target global critical infrastructure.
TL;DR
The SafePay ransomware group is actively targeting critical infrastructure globally using sophisticated lateral movement and data exfiltration techniques. This advisory provides technical details on their use of legitimate system tools to bypass security and encrypt victim files.
This joint advisory from CISA, the FBI, and international partners outlines the operational patterns of the SafePay ransomware group, which has been highly active since August 2024. The threat actors primarily gain entry into networks via credential exposure, brute-force attacks, and the exploitation of edge device vulnerabilities, specifically leveraging phished accounts through Mullvad VPN IP addresses. Once access is established, the group employs 'Living off the Land' (LotL) tactics to maintain persistence and escalate privileges, often using tools like PsExec and WinRM to execute commands remotely. To identify high-value targets for exfiltration, they utilize specialized scripts such as ShareFinder.ps1 and SharpShares.exe to enumerate network shares within Active Directory environments. During the lateral movement phase, the actors use RDP and various administrative tools to expand their footprint while simultaneously disabling security software to avoid detection. For data theft, SafePay utilizes a variety of legitimate utilities including RClone, WinSCP, and 7-Zip, sometimes even using cloud services like OneDrive for exfiltration. To ensure maximum impact and prevent recovery, the group actively targets backups by halting the Volume Shadow Copy Service and resetting Network Attached Storage (NAS) devices to factory defaults. Organizations are urged to implement Zero Trust principles, enforce multi-factor authentication (MFA), and maintain rigorous patching schedules for all internet-facing systems.
Mullvad VPN
PsExec
Windows Remote Management (WinRM)
PowerShell
ShareFinder.ps1
SharpShares.exe
Remote Desktop Protocol (RDP)
FileZilla
7-Zip
RClone
WinRAR
WinSCP
OneDrive
AnyDesk
TeamViewer
Active Directory
Read full article →
Article 10
Philip R. Lane: Euro liquidity lines and the international monetary system
The role and expansion of international liquidity lines, specifically EUREP and swap lines, in supporting the Eurosystem's monetary policy transmission.
TL;DR
The ECB is enhancing its international liquidity framework through the expanded EUREP facility and strategic swap lines to ensure smooth monetary policy transmission. These tools are designed to provide backstop liquidity to foreign central banks, thereby stabilizing euro-denominated bond markets and reducing global financial spillovers.
In a recent address, Philip R. Lane of the ECB detailed the critical importance of international liquidity lines in maintaining the stability of the Eurosystem. Because the ECB's primary refinancing operations are limited to domestic counterparties, international lines—comprising both repo and swap arrangements—are essential to prevent cross-border liquidity shortages from impacting euro money market rates and securities markets. A significant development is the enhancement of the Eurosystem repo facility for central banks (EUREP), which allows non-euro area central banks to access euro liquidity against high-quality euro-denominated collateral. This updated framework, expected to be fully operational by the fourth quarter of 2026, introduces standing access for eligible central banks and aims to support the functioning of euro-denominated debt markets globally. EUREP is expected to encourage foreign central banks to hold a wider variety of euro area sovereign and supranational bonds, thereby enhancing market integration. Complementing this, swap lines provide a different transmission channel by allowing liquidity against local-currency collateral, which is particularly effective in supporting the bank credit channel. While swap lines carry higher risks and are restricted to highly-rated sovereigns to prevent moral hazard, they serve as vital signaling tools to reduce global financial crises. Ultimately, these liquidity mechanisms strengthen the international role of the euro by fostering confidence in its use for trade invoicing, settlements, and expanded debt issuance.
EUREP (Eurosystem repo facility for central banks)
Main Refinancing Operations (MRO)
Longer-Term Refinancing Operations (LTRO)
Asset Purchase Programme (APP)
Pandemic Emergency Purchase Programme (PEPP)
Read full article →
Article 11
Asymptotically good bosonic Fock state codes
The development of asymptotically good bosonic Fock-state codes designed to correct amplitude-damping noise in the large excitation regime.
TL;DR
This research introduces a new class of bosonic Fock-state codes capable of maintaining error-correction properties in the asymptotic regime under amplitude-damping noise. By leveraging random classical codes in a discrete simplex, the authors provide a solution for protecting against constant loss parameters while improving coherence lifetimes.
The paper addresses a critical limitation in current quantum error correction: the inability of existing bosonic Fock-state code families to protect against amplitude-damping (AD) noise when the number of photon losses scales linearly with the total excitation. In the asymptotic regime, where the total excitation grows without limit, previous constructions only provided protection against sublinear photon losses. To bridge this gap, the authors propose a construction of asymptotically good Fock-state codes based on random classical codes within a discrete simplex. A significant innovation in this approach is that randomness is introduced via the classical indexing structure rather than through traditional quantum code randomization methods. This specific method of randomization yields the beneficial property of bounded per-mode occupancy, which effectively limits the number of photons in any single mode and subsequently enhances the coherence lifetime of the encoded states. Furthermore, the research demonstrates that these findings are not limited to bosonic systems; through a mathematical relationship between Fock-state codes and permutation-invariant codes, the authors also derive asymptotically good families for qudit permutation-invariant codes and codes within monolithic nuclear state spaces.
Article 13
Interactive proofs for verifying (quantum) learning and testing
The research explores the use of interactive proofs and quantum communication to enable resource-constrained users to verifiably delegate quantum learning and testing tasks to untrusted, powerful providers.
TL;DR
This paper investigates whether resource-constrained learners can use interaction with untrusted parties to improve the efficiency of quantum learning and testing. It concludes that while classical communication is insufficient for verification, quantum communication enables significant advantages in delegating tasks to powerful providers.
The research addresses a critical challenge in the emerging era of distributed quantum computing: how users with limited computational resources can verify the results of complex tasks delegated to powerful but untrusted data centers. As quantum hardware becomes concentrated in large-scale facilities, the need for verifiable delegation grows, particularly for machine learning and testing problems where the provider possesses high-quality data inaccessible to the client. The authors present a dual-sided finding: first, an impossibility result demonstrating that classical interaction cannot empower a resource-constrained learner to verify answers from a more powerful prover in many scenarios; second, a positive result showing that quantum communication enables memory-constrained verifiers to leverage the multi-copy processing capabilities of untrusted provers. This work establishes a foundational theory for verification in quantum learning and testing, highlighting that a quantum internet—capable of supporting quantum communication—is a necessary component for the secure delegation of these advanced computational tasks.
Article 14
The distroless security gap: Why bottom-up containers are the next evolution in OCI images
The evolution of container security from 'distroless' trimming to 'bottom-up' assembly to resolve the conflict between attack surface reduction and vulnerability visibility.
TL;DR
The article explores the 'distroless security gap' where minimizing container size inadvertently breaks vulnerability scanning by removing package metadata. It proposes a shift toward bottom-up, declarative container assembly to achieve both minimal attack surfaces and full security auditability.
The current state of container security is caught in a paradox between bloated images and un-scannable 'distroless' images. While traditional containers include unnecessary shells and package managers that expand the attack surface, the industry's move toward distroless images has introduced a significant blind spot: the removal of OS package metadata makes it impossible for scanners like Trivy to accurately detect vulnerabilities. This creates a compliance liability where an image may be small but cannot be mathematically proven safe. To solve this, the article advocates for a 'bottom-up' assembly method rather than top-down trimming. This new paradigm uses three distinct stages: first, 'precision slicing' via tools like Chisel to extract only necessary package components from trusted archives; second, 'declarative builds' using tools like Rockcraft to define the container state via YAML instead of imperative Dockerfiles; and third, 'runtime management' using lightweight managers like Pebble to act as PID 1. This approach ensures that minimal containers remain auditable, stable, and secure without sacrificing developer experience or operational visibility.
Article 15
Palo Alto's firewall OS has been under attack from multiple ransomware groups since June
Ransomware groups are actively exploiting a high-severity authentication bypass vulnerability in Palo Alto Networks' PAN-OS to infiltrate diverse industries.
TL;DR
Multiple ransomware groups are exploiting a critical authentication bypass vulnerability in Palo Alto Networks' PAN-OS to penetrate corporate networks. The attacks involve sophisticated lateral movement and attempts to compromise virtualization layers to evade endpoint detection.
Since June, various ransomware operations, including Qilin, Inc, and Settra, have been actively exploiting CVE-2026-0257, a high-severity authentication bypass vulnerability affecting Palo Alto Networks' PAN-OS GlobalProtect portals and gateways. Although a patch was released in mid-May, threat intelligence from Unit 42 confirms that attackers are successfully bypassing multi-factor authentication (MFA) to establish unauthorized VPN sessions. Once initial access is secured, the threat actors utilize protocols such as RDP and SMB for lateral movement across infected environments. A particularly sophisticated tactic identified involves pivoting from the compromised VPN gateway directly to the virtualization management layer, specifically targeting vCenter and ESXi hypervisors. By manipulating security controls on ESXi, attackers have been observed performing offline credential dumping against domain controller virtual disks (VMDK), effectively bypassing in-guest endpoint detection and response (EDR) solutions. The scope of the impact is widespread, affecting critical industries including healthcare, finance, manufacturing, and government. Furthermore, researchers have noted that attackers are chaining this PAN-OS exploit with other vulnerabilities, such as CVE-2023-27532 targeting Veeam backup infrastructure, to deepen their persistence and maximize data theft capabilities.
Palo Alto Networks PAN-OS
GlobalProtect
Qilin Ransomware
Inc Ransomware
Settra Ransomware
Remote Desktop Protocol (RDP)
Server Message Block (SMB)
vCenter
ESXi hypervisors
VMDK
Veeam
CVE-2026-0257
CVE-2023-27532
Read full article →
Article 16
PHP2Shell (CVE-2026-109618/109619): first exploit requests arrived 5.5 hours before PHP shipped the fix, and the "scanners" carry Mirai-style loaders
Discovery and analysis of two critical unauthenticated Remote Code Execution (RCE) vulnerabilities in PHP core, known as PHP2Shell.
TL;DR
Two critical RCE vulnerabilities, CVE-2026-109618 and CVE-2026-109619, have been identified in the PHP core, allowing unauthenticated attackers to execute code via multipart form manipulation. The flaws are being actively exploited by automated scanning tools following a leak of proof-of-concept material.
The article details the emergence of 'PHP2Shell,' a pair of critical vulnerabilities (CVE-2026-109618 and CVE-2026-109619) in the PHP engine, both carrying a CVSS score of 9.2. The first vulnerability, CVE-2026-109618, leverages memory corruption during Out-of-Memory (OOM) events caused by specifically crafted multipart/form-data requests, such as deeply nested field names or excessive headers. The second, CVE-2026-109619, exploits stale global state left in worker processes after a request terminates unexpectedly, specifically via the session upload progress feature. Technical analysis of observed traffic shows that attackers are using automated tools to scan for these flaws, with some payloads attempting to download and execute 179KB ELF binaries. The report highlights that while patches are available for supported PHP branches (8.2 through 8.5), users on older, unsupported versions like PHP 8.1 or 7.x remain permanently vulnerable and must migrate. Mitigation strategies include setting memory limits via cgroups, disabling session upload progress, and implementing front-end restrictions on multipart/form-data uploads.
Article 17
Linus Torvalds Eliminates Unsafe __get_user() & __put_user() Functions In Linux 7.4
Linus Torvalds has merged a patch into the Linux kernel to remove the historically unsafe and unvalidated __get_user() and __put_user() functions.
TL;DR
Linus Torvalds has officially removed the unsafe __get_user() and __put_user() functions from the Linux kernel to improve security and performance. The update leverages modern scoped access helpers and utilized AI-assisted coding techniques for the transition.
In a significant move toward hardening the Linux kernel, Linus Torvalds has merged code that eliminates the long-standing __get_user() and __put_user() functions. These specific functions were historically used to copy variables between user-space and kernel-space but were inherently dangerous because they bypassed critical pointer validation checks regarding the user address range. Beyond the security risks, Torvalds noted that these functions are actually less efficient than the modern get_user() and put_user() alternatives. The removal process has successfully cleared these remnants from the x86/x86_64 architecture, though some architectural ports like ARM64 may still have lingering traces due to existing mappings. Notably, this development highlights a growing trend in kernel maintenance through the use of AI; Torvalds mentioned using Claude Code as an advanced tool for source-to-source transformations, similar to how one might use Coccinelle scripts for static analysis. This patch marks a major step in cleaning up 'historical horrors' within the kernel codebase by enforcing the use of safer, scoped user access region helpers.
Article 18
Lazarus hackers use post-quantum cryptography for malware delivery
The Lazarus Group is utilizing post-quantum cryptographic mechanisms like ML-KEM to secure malware delivery in a new campaign dubbed FlashHole.
TL;DR
North Korean hackers from the Lazarus Group have launched a sophisticated campaign named FlashHole that employs post-quantum cryptography to hide malicious payloads. The operation targets South Korean industries by exploiting legitimate software and using advanced encryption standards to bypass traditional detection.
The Lazarus Group has introduced a highly sophisticated attack chain, identified as Operation FlashHole, which distinguishes itself through the implementation of post-quantum cryptographic (PQC) mechanisms. According to research from Kaspersky, the threat actors are utilizing the ML-KME-1024 algorithm—a NIST-approved standard designed to resist future quantum computing attacks—to secure communications between infected hosts and command-and-control (C2) infrastructure. The attack begins with phishing pages that redirect users to specially crafted GitHub repositories, initiating an in-memory execution chain. This chain exploits the INISAFE CrossWeb EX security tool and the legitimate Windows 'fsquirt.exe' utility to execute shellcode.
The malware ecosystem involved in this campaign is multi-layered. LPEClient serves as a primary component that receives public keys from the C2 server, generates shared keys, and facilitates the decryption of incoming payloads. ClientHub acts as a loader capable of communicating via Dropbox or direct exchange with LPEClient. The ultimate payload, Cubridge, is a modular backdoor providing attackers with capabilities for file management, reconnaissance, and screenshot capturing. To further obfuscate the process, the group employs a complex encryption hierarchy where ciphertexts are encrypted with the GOST algorithm, and shared secrets provide key material for the Threefish algorithm.
By utilizing in-memory execution and advanced cryptographic standards, the Lazarus Group aims to minimize detection risks and ensure that even if traffic is intercepted, it remains undecipherable by current means. The campaign has already impacted several sectors in South Korea, including software, construction, and manufacturing. This evolution in tactics suggests a strategic move toward 'harvest now, decrypt later' resilience, ensuring their command infrastructure remains robust against advancing decryption technologies.
ML-KEM-1024
LPEClient
ClientHub
Cubridge
INISAFE CrossWeb EX
Windows fsquirt.exe
GOST algorithm
Threefish
GitHub
Dropbox
Chromium-based browsers
Read full article →
Article 19
Carbon-X is an open 14.8B model trained jointly on DNA and text
The release of Carbon-X, an open 14.8B parameter language model designed for joint DNA sequence understanding and natural language processing.
TL;DR
HuggingFaceBio has introduced Carbon-X, a 14.8B parameter decoder-only model specialized in processing both DNA sequences and natural language. The model demonstrates state-of-the-art performance in genomic tasks like variant effect prediction while maintaining high inference efficiency.
Carbon-X is a newly released 14.8B parameter language model from the Carbon family, specifically engineered for biological sequence analysis. Unlike traditional models that use separate encoders, Carbon-X utilizes a single decoder architecture with a hybrid tokenizer. This tokenizer integrates standard BPE vocabulary for natural language with a specialized system that encodes DNA as non-overlapping 6-mers, allowing the model to process raw DNA directly within a chat interface. The model's capabilities include predicting whether mutations are benign or pathogenic, identifying regulatory regions, and performing next-base prediction. In evaluations across five DNA benchmarks, Carbon-X achieved an average score of 66.7%, significantly outperforming Qwen3-14B and rivaling frontier models like GPT-6.1 Sol at a fraction of the cost. For example, analyzing 2.4 million variants in ClinVar is estimated to cost only $300 with Carbon-X, compared to potentially millions of dollars using larger proprietary models. Technically, the model features 40 layers, GQA, and SwiGLU activation, with a context window of 40,960 tokens. Because the weights can fit on a single 80 GB GPU, it provides an ideal solution for researchers needing to process sensitive or unpublished genomic data on private infrastructure. The model is optimized for efficient serving using vLLM and supports automated DNA tagging within prompts.
Article 20
US Government Funded Quantum Finance Initiatives to Safeguard Risk Modeling, Portfolio Optimization, Cryptography, Q-Day
The U.S. government is implementing multi-billion dollar funding initiatives and federal mandates to protect the financial sector from quantum computing threats, specifically targeting 'Q-Day' readiness.
TL;DR
The United States is deploying massive federal funding and regulatory mandates to safeguard the financial system against the cryptographic risks posed by future quantum computers. This strategy involves a coordinated effort between the Treasury, NIST, CISA, and the NSA to transition critical infrastructure to post-quantum standards.
The U.S. government has launched an aggressive multi-billion dollar strategy to defend the nation's financial architecture against 'Q-Day,' the point at which cryptanalytically relevant quantum computers (CRQCs) can break classical public-key encryption. Under Executive Orders 14412 and 14413, the federal strategy focuses on both economic risk management and technical cybersecurity. A significant component of this effort is the $2 billion allocation from the CHIPS & Science Act, which provides venture equity in quantum computing leaders such as IBM, D-Wave, and Rigetti to bolster domestic hardware foundations for risk modeling and portfolio optimization. The Department of the Treasury, acting as the Sector Risk Management Agency, has established a Quantum-Readiness Task Force to oversee the migration of banks, payment processors, and insurance networks toward quantum-safe systems. Simultaneously, NIST is tasked with the mathematical standardization of Post-Quantum Cryptography (PQC) algorithms, while CISA leads the operational execution of these migrations across critical infrastructure, enforcing a deadline for software upgrades by late 2030. The NSA provides essential intelligence regarding 'Harvest Now, Decrypt Later' threats from state-sponsored actors, ensuring that national security systems and the defense industrial base are prepared for the quantum era.