LesenForschungRadarAnlageframework
Anmelden / Registrieren
AlleTechnikProdukteInvestierenBörseSonstiges

Lesen

2026-11-19129 Beiträge

Aktualisieren

Security firm Barracuda discloses AI-driven cloud breach: Attackers used ARTEX framework to compromise 10 accounts in 44 hours

Wesentlich
2026-11-19 09:55 GMT+8

Cybersecurity firm Barracuda Networks has disclosed a significant security incident in which attackers used an artificial intelligence framework to autonomously breach its cloud environment. According to the company’s investigation, the attackers utilized the AI penetration testing tool ARTEX to traverse 10 cloud accounts within 44 hours, continuously harvesting credentials, exploring internal systems, and attempting to establish backdoors.

The initial entry point was a cloud access key that Barracuda had previously provided to a third-party AI company for a project but failed to revoke after the engagement ended. In October 2026, the development environment of this AI vendor was compromised, allowing attackers to steal the dormant key. On November 1, the attackers began using the key to explore accessible resources, extracting stored AWS access keys and Azure service principal secrets.

Over the next 24 hours, the AI-driven attack system leveraged these stolen credentials to progressively infiltrate data analysis systems, source code access tokens, and Kubernetes clusters. By early November 2, the attackers pushed short-lived branches to several code repositories, triggering build workflows that leaked sensitive information from the build system into job logs. The AI also searched for cryptocurrency wallet information on servers with shell access and attempted to create new cloud administrator identities, though this latter attempt failed.

Barracuda detected anomalous account activity on November 4 and connected the events after receiving notification of the security incident from the third-party AI company. While no direct access to Barracuda XDR customer data has been confirmed, incomplete event logs mean the company cannot rule out potential exposure. Barracuda has since rotated all potentially affected credentials and notified some customers to revoke and re-establish API integration keys.

This incident highlights the growing risk of AI agents executing complex, multi-stage attacks at machine speed. Unlike traditional breaches reliant on manual exploitation, the use of ARTEX allowed for rapid lateral movement and credential harvesting across multiple cloud environments, underscoring the critical need for strict lifecycle management of third-party access keys.

Quellen:iThome

Forschung

Texas Instruments Integrates AI Agents into CCStudio IDE to Automate Embedded Development

Wesentlich
2026-11-19 19:00 GMT+8

At the electronica 2026 trade show in Munich, Texas Instruments (TI) unveiled a new capability in its integrated development environment (IDE), Code Composer Studio (CCStudio). The update integrates AI agents directly into the development workflow, allowing them to automate tasks ranging from peripheral configuration and code generation to real-hardware debugging.

Traditional generative AI tools often struggle with embedded software development because they lack access to hardware-specific information, leading to code that builds successfully but fails on actual devices due to incorrect pin mappings or clock settings. TI addresses this by providing SDKs, pin configurations, and peripheral data to AI agents through Model Context Protocol (MCP) servers. This enables the agents to understand TI device specifications and execute complex operations including application building, flashing to devices, and initiating debug sessions to diagnose hardware or memory states.

During a demonstration, TI showed how an AI agent could generate a functional snake game for a microcontroller in approximately ten minutes without the developer writing any code. The agent automatically configured peripherals like joysticks and displays based on natural language instructions. TI emphasized that this feature works with existing third-party AI agents such as Anthropic's Claude Code, OpenAI's Codex, and Microsoft Copilot, rather than requiring a proprietary TI AI model. The functionality is available across TI's general-purpose and real-time MCUs, wireless devices, and radar SoCs.

Quellen:EE Times Japan

Forschung

Open-source project blender-skills packages Blender workflows as AI agent skills for natural language 3D scene generation

Kurzfassung
Verifiziert 2026-11-19 10:47 GMT+8

The open-source project blender-skills on GitHub has packaged common 3D production workflows in Blender into 28 "skills" callable by AI agents. Once installed, users can describe desired 3D scenes in natural language within programming assistants like Claude Code or Codex, prompting the agent to automatically invoke Blender scripts for modeling, material adjustment, lighting setup, and final rendering.

These skills cover the entire pipeline from hard-surface modeling, UV unwrapping, PBR materials, and rigging to animation and exporting to game engines like Unity, Unreal, and Roblox. The project requires Blender 5.2 LTS or newer, with version 5.3.0 recommended for best compatibility. For users without 3D software experience, the value of such skill packs lies in eliminating the need to learn complex Blender interfaces and Python scripts, allowing AI to execute tasks according to professional workflows, though the quality of the final output still requires human judgment.

Quellen:GitHub

Forschung

OpenAI Partners with French Media Group Le Figaro to Surface Journalism in ChatGPT via Summaries and Excerpts

Thema · OpenAI–Le Figaro PartnershipKurzfassung
2026-11-18 08:00 GMT+8

US-based AI company OpenAI and French media group Le Groupe Figaro announced a strategic partnership on November 18, 2026. The collaboration covers current reporting and archive content from Le Figaro and associated publications spanning news, business, culture and lifestyle, discoverable in ChatGPT using summaries and excerpts with links to underlying stories. Le Figaro retains full editorial independence. Financial terms were not disclosed.

Quellen:OpenAI

Forschung

OpenAI Reports Silicon-Proven PPA Gains in Jalapeño and AMD Designs, Announces Synopsys Partnership for EDA Integration

Wesentlich
2026-11-18 08:00 GMT+8

On November 18, 2026, OpenAI published research updates stating that its frontier models, including GPT-6 Astra, have delivered "silicon proven" power, performance, and area (PPA) optimizations in both its custom inference chip, Jalapeño, and AMD's flagship GPU and CPU designs. This follows an initial August disclosure regarding Jalapeño's early results.

For the Jalapeño chip, OpenAI's team estimates that model-proposed changes reduced standard-cell area by approximately 13% in the vector unit and 10% in the matrix unit. Specific examples include a multiplier redesign that cut cell area by about 15% while reducing latency from two clock cycles to one, and an adder redesign that also saved 15% area while maintaining two-cycle latency. These optimizations were verified during Jalapeño's silicon bring-up.

In collaboration with AMD, OpenAI reported that its models achieved up to 14% PPA improvement relative to heavily optimized baselines on AMD's flagship GPU IP by rewriting SystemVerilog RTL code. AMD has incorporated some of these changes into recent manufacturing submissions and added others to production files for future versions. Additionally, AMD verified single-digit percentage PPA gains in key blocks of its upcoming next-generation flagship CPU using designs written by OpenAI's models.

To measure capability progression, OpenAI benchmarked successive model generations on two open-source RISC-V cores: PicoRV32 and Ibex. Results showed that GPT-6.2 Astra achieved the highest average scores at comparable token budgets (~112,000 tokens). Notably, all tested models performed better when designing cores from scratch based on specifications than when optimizing existing RTL, suggesting strong architectural exploration capabilities.

Looking ahead, OpenAI announced a partnership with Synopsys, a leader in electronic design automation (EDA). They are training a new model, GPT-Synopsys, designed to use Synopsys EDA tools as expert chip designers do, aiming to integrate frontier AI directly into established engineering workflows.

Quellen:OpenAI

Forschung

Ant Group and Westlake HeartChen Open-Source Duo v1: A Reciprocal World Model Where Virtual Agents Autonomously Decide When to Speak or Listen

Thema · Duo v1 Reciprocal World ModelWesentlich
2026-11-18 23:00 GMT+8

According to a report by Zhidongxi on November 18, Ant Group's Technology Research Institute and Hangzhou-based large model company Westlake HeartChen released and open-sourced the Reciprocal World Model (RWM) Duo v1 on November 17. The model integrates an intelligent agent into the world through two tightly coupled modules: Intent and Realization. It allows virtual agents to continuously receive user audio and video inputs, autonomously decide when to speak or listen, and generate corresponding sounds and visuals in real time for interaction.

Traditional world models typically simulate only physical scenes such as lighting, materials, and dynamics, lacking an internally responsive agent. Duo v1 covers both physical reality and the intelligent agent, sharing the same interactive spatiotemporal space. Within each approximately 0.7-second chunk, the Intent module autonomously decides whether to speak or wait based on user input and interaction history, generating corresponding language content. The Realization module then combines the hidden state from Intent, user input, and its own generated historical content to produce matching audio and video.

In human evaluations across 30 sets of real interactions, Duo v1 passed 168 out of 180 checks, achieving an overall pass rate of 93.3%. Specifically, the pass rates for language adherence, speech intelligibility, and visual identity stability were all 100%, while content responsiveness was 73.3%. Content responsiveness and long-term consistency remain the main challenges for the current version. The technical report, training code, and model weights for Duo v1 are now publicly available for developers to download and build upon.

Quellen:zhidx.com

Forschung

Databricks launches Unity Gateway Insights to auto-analyze AI agent costs

Wesentlich
2026-11-19 06:42 GMT+8

US data intelligence company Databricks announced the launch of Unity Gateway Insights on November 18, 2026, a new feature designed to automatically analyze millions of AI agent traces alongside business data to identify cost inefficiencies. The tool aims to move beyond simple budget caps by using Genie, Databricks' AI assistant, to pinpoint where tokens are being wasted in enterprise coding workflows.

According to the announcement, trace analysis at Databricks revealed several specific opportunities for savings. For instance, fixing seven small bugs in their Model Context Protocol (MCP) servers recovered an estimated $1.2 million in costs annually. These bugs caused agents to retry failed tool calls repeatedly, leading to significant wasted tokens and engineer waiting time. Additionally, the analysis showed that simple prompts were often routed to expensive frontier models, prompting the adoption of Smart Routing to direct routine tasks to cheaper alternatives.

Unity Gateway Insights integrates with the existing Unity Gateway control plane. When developers use coding agents like Claude Code or GitHub Copilot via the ug CLI, the system automatically captures OpenTelemetry traces into a unified table. The Insights feature then generates reports answering questions such as which workstreams consume disproportionate tokens and which repeated workflows could be codified into shared skills. This allows teams to see exactly how much each type of waste costs them.

Quellen:Databricks

Forschung

Neo4j Product Lead: Load Git History as a Graph Database, So Coding Agents Can Find Unreferenced File Coupling in Source Code

Wesentlich
2026-11-19 05:00 GMT+8

The security directory in FastAPI contains four modules: api_key.py, oauth2.py, http.py, and open_id_connect_url.py. They do not import each other, and there are no clues in the source code pointing to one another. However, git history reveals that among the 28 commits modifying api_key.py, oauth2.py changed in 18 of them, http.py in 17, and open_id_connect_url.py in 16. Every time someone added behavior to one security scheme—auto_error, description parameter, 401 status code, or WebSocket support—all four modules moved together.

William Lyon, Neo4j’s product lead, used Relate’s git-to-graph extension to import FastAPI’s 8,102 commits into a graph database, then used fs-to-graph to import the working tree, exposing it to coding agents via MCP in read-only mode. He tasked Codex, OpenCode, and Pi with two assignments under two conditions: adding an optional constructor argument to APIKeyHeader, and adding a keyword argument to APIRouter.add_api_route. For each task, the agent had to first answer which other files needed changing, which tests to run, and who should review. When able to read only the source code tree, none of the three agents mentioned the three sibling security modules; after accessing the graph, all three found them and provided specific counts.

This gap is not an isolated case. Lyon queried all file pairs within the FastAPI package that co-changed at least five times, finding 126 pairs, of which 42—about one-third—contained no textual reference to each other in their file contents. This means that regardless of following import chains or searching for filenames, a static source code tree cannot expose this coupling. A graph database turns historical patterns into questions answerable by Cypher queries: What files change along with mine? Has anyone made this kind of change before? Who recently touched these files?

Boundaries to retain: This is a controlled test built, executed, and reported by Neo4j itself, constituting vendor self-testing without independent replication. The repository contained only FastAPI, and the model used was only gpt-6.1-sol. The count of 42 pairs is based on filename matching in text rather than a true import graph, and Lyon himself acknowledges this number is approximate. It proves that for three categories of problems—file coupling, change precedents, and reviewer identification—the answers exist in commit history rather than code text. The source code tree structure cannot provide this information not because it hides it, but because the code itself does not record who changed things together.

Quellen:Neo4j Graph Intelligence Platform

Forschung

Anthropic's Quarterly Compute Spending Nears $10 Billion, with Roughly Half Flowing to SpaceX

Thema · Anthropic Compute & SpaceXWesentlich
2026-11-18

Anthropic spent nearly $10 billion on compute and infrastructure in the third quarter of 2026, or close to $40 billion on an annualized basis. This figure comes from the S-1/A filing submitted to the U.S. Securities and Exchange Commission (SEC) for its initial public offering (IPO), marking the first time that a frontier AI laboratory has publicly disclosed compute spending details with quarterly granularity.

More noteworthy is the structure of the expenditure: Anthropic paid approximately $5 billion to SpaceX during the quarter, representing nearly half of its total compute spending. This ratio was confirmed by Bloomberg in late October 2026—Anthropic accounted for 34.5% of SpaceX's total revenue in Q3 2026, corresponding to about $5 billion. This means that Anthropic's reliance on a single supplier far exceeds previous estimates based on annual aggregate data.

In terms of growth trajectory, Anthropic's compute spending rose from $433 million for the full year of 2023 to $9.863 billion in Q3 2026 (annualized at $39.45 billion), representing an average annual growth rate of approximately four times over three years. Epoch AI's comparative analysis shows that OpenAI maintained a roughly threefold annual growth rhythm during the same period: approximately $5.8 billion for the full year 2024, $16.3 billion for 2025, and President Greg Brockman testified in May 2026 that he expected full-year spending to reach about $50 billion.

The absolute scale gap between the two companies is narrowing. In 2024, Anthropic's annualized compute spending was approximately $2.5 billion, only 43% of OpenAI's; by Q3 2026, Anthropic's annualized spending had reached approximately $39.5 billion, approaching 80% of OpenAI's full-year forecast. If Anthropic maintains its current quarterly growth rate, its annualized spending could equal OpenAI's by the end of 2026 or early 2027.

Future commitments indicate that competition will not slow down. Anthropic's S-1 disclosure revealed compute contract commitments of $447.5 billion (from September 2026 through the end of 2030), averaging about $100 billion per year. On the OpenAI side, according to Yahoo Finance, it plans to invest approximately $750 billion over the same period. These figures far exceed current actual expenditures, meaning both companies are locking in supply for compute expansion over the next several years.

For industry observers, this set of data reveals a structural feature that had previously been vaguely handled: the compute spending of frontier AI laboratories is highly concentrated among a few suppliers, and this concentration is still rising. Anthropic's suppliers include Amazon, Google, Microsoft, and SpaceX, but SpaceX alone accounted for nearly half of its spending in Q3 2026. Epoch AI points out that a significant portion of Anthropic's compute spending growth can be attributed to the expansion of transactions with SpaceX, while SpaceX itself is also rapidly entering the compute rental market.

Quellen:Epoch AI

Forschung

Analyst Zeus Kerravala: Multi-Availability Zones Prevent Component Failures, Not Total Service Outages

Thema · Zeus Kerravala Resilience ArchitectureWesentlich
2026-11-19 09:21 GMT+8

Between November 12 and 17, 2026, six major IT outages occurred over six days: Microsoft 365 experienced a global outage lasting nearly 24 hours; Workday inadvertently connected its disaster recovery environment to production databases; the U.S. Federal Aviation Administration issued a nationwide ground stop due to router overload; United Airlines delayed flights because it could not obtain aircraft weight data; JPMorgan Chase suffered customer transfer failures due to local hardware and software defects; and Apple experienced outages affecting iCloud and Apple Pay due to an internal update. While the root causes varied—a dormant bug, overloaded routers, a faulty internal update, and local hardware failure—the pattern was identical: a critical dependency failed, and business operations stopped. ZK Research Principal Analyst Zeus Kerravala argues from this that availability architecture and resilience architecture are not the same thing. The former keeps services running when components fail; the latter keeps businesses running when an entire service fails. Most companies possess the former but mistakenly believe they have the latter.

Kerravala points out that cloud computing has caused the industry to forget disaster recovery discipline. In the financial services sector, maintaining both a production data center and a disaster recovery (DR) data center is non-negotiable standard practice. As the world shifted to the cloud, many assumed disaster recovery became the responsibility of the cloud provider; however, it remains a shared responsibility. Availability zones and multi-region designs protect against hardware failures and localized events, but these environments share software, control planes, configuration pipelines, and DNS. When a bad configuration or a dormant bug propagates, it spreads everywhere—as seen with Microsoft’s July network gateway bug, which cascaded across 74 countries and territories.

Kerravala cites Zscaler’s Business Continuity Cloud as a concrete example of what fate separation requires. This environment operates in third-party data centers rather than Zscaler’s own facilities, utilizing independent networks, autonomous system numbers, DNS, and cloud domains. Software and threat intelligence updates are deliberately staggered so that a defective production release does not simultaneously land in the backup. Policy and identity data sync unidirectionally into a read-only, last-known-good state. Spanning nine regions, the architecture is sufficient to maintain domestic operations if a nation were cut off. Zscaler also encourages customers to route synthetic or trusted user traffic to the backup environment continuously during peacetime, validating the failover path daily rather than testing it only during annual tabletop exercises. Failover can be triggered automatically or manually by the customer, ensuring functionality even if Zscaler itself becomes unreachable.

Kerravala’s conclusions are directed at buyers: define the minimum viable business, identifying three to five workflows that must continue running along with all their dependencies; interrogate each key vendor’s continuity architecture—if the answer is 'multiple availability zones,' that indicates availability, not continuity; test continuously rather than relying on annual exercises; keep security capabilities online during crises, as attackers will act immediately when defenses are relaxed; and leverage buyer power at renewal time by making fate-separated continuity a contractual requirement. He acknowledges that Zscaler cannot keep Microsoft mailboxes online or restart FAA routers; its architecture serves merely as a continuity model for its own platform, not a panacea.

Quellen:SiliconANGLE

Forschung

Palo Alto Networks Survey: Over 70% of Enterprises Allow AI Agents to Modify Code, but Less Than 10% Can Fully Detect Unmanaged AI Activity

Thema · AI Agent Identity ManagementWesentlich
2026-11-19 08:00 GMT+8

Cybersecurity firm Palo Alto Networks recently published its "2026 State of Cloud-Native Security" report, revealing that while AI agents are ubiquitous in enterprise software development, security measures have failed to keep pace. Nearly all surveyed organizations use AI agents in their software development lifecycle, and more than 70% allow these agents to modify code, adjust Continuous Integration/Continuous Delivery (CI/CD) settings, or make changes to production environments. However, less than 10% of respondents can comprehensively detect and classify unmanaged AI activity across different cloud environments.

The introduction of AI-assisted development has significantly increased the frequency of infrastructure changes. Over 80% of surveyed organizations reported that AI agents lead to more frequent cloud infrastructure modifications, yet fewer than 40% enforce mandatory manual security reviews. Additionally, only about 30% of organizations can track the complete process from code commit to deployment execution for most production workloads. Regarding Infrastructure as Code (IaC), more than 40% of organizations use AI to generate IaC templates, but only about 30% require mandatory security scanning before deployment. Data shows that during a 90-day period, an average of nearly 20% of high-severity application security issues made it into production, with the average time from discovering a code security issue to deploying a patch exceeding 18 days.

Identity management for AI agents presents another critical vulnerability. Nearly 40% of surveyed organizations admitted that their AI development tools or agents can access production cloud environments through development or deployment pipelines. More concerning is that over half of the responding engineers stated that AI agent operations are attributed to the engineer's own identity or personal access tokens, rather than a distinct AI agent identity. This makes it difficult for enterprises to distinguish human actions from machine behaviors during audits, and 40% of organizations cannot reconstruct what operations an AI agent performed, hindering their ability to confirm whether the agent accessed sensitive resources or exceeded its intended scope.

Credential management also suffers from significant gaps. 30% of surveyed organizations discovered that credentials used by AI agents in CI/CD pipelines were not included in enterprise management systems. Over 30% reported difficulty in revoking or rotating credentials used by AI agents during security incident investigations, while 60% still require manual intervention to revoke access rights for Nonhuman Identities (NHI). Data leakage risks are also rising: about 20% of organizations only discover shadow AI after an incident or audit, 40% have found managed data copied to unmanaged AI environments, and nearly 40% have identified sensitive or regulated data being used for AI model training or fine-tuning without authorization.

Quellen:iThome

Forschung

Cloudflare Releases Open-Weight Clairic and Clairic-flash Extraction Models with Parallel Slot Autoregressive Architecture

Wesentlich
2026-11-19 06:00 GMT+8

US cloud computing company Cloudflare announced on November 18, 2026, that its Workers AI Superintelligence team has released two new open-weight extraction models: an updated version of Clairic and a new lightweight variant called Clairic-flash. Both models are now hosted on Workers AI, with full open weights available for download on Hugging Face.

This release marks Clairic's graduation from preview status. Cloudflare stated that the new version of Clairic features a redesigned architecture using "parallel slot autoregressive generation" instead of the previous single forward pass. In this new mechanism, each field uses tokens it has already written to choose its next token, stopping at its own end marker, while all fields advance together in the serving batch. This change aims to improve accuracy in text and image extraction while maintaining low latency.

In addition to the architectural upgrade, Cloudflare introduced Clairic-flash, a lighter and faster version with 9 billion parameters designed for compact deployment. According to internal evaluation data published by the company, Clairic-flash performs strongly across various extraction tasks; for example, in mixed-input field internal evaluations, Clairic-flash scored 213/226, compared to 156/226 for the older preview model. It should be noted that these benchmarks are vendor self-reported results and have not yet been independently reproduced by third parties.

Regarding pricing, Cloudflare adjusted its "System One" model billing strategy. The 27B-parameter Clairic model is priced at $0.24 per million input tokens, while the 9B-parameter Clairic-flash is priced at $0.10 per million input tokens. To facilitate migration, Cloudflare offers a limited-time promotion: until December 1, 2026, both models will be billed at $0.10 per million input tokens. After this date, Clairic will return to its standard price.

Cloudflare emphasized that despite the architectural changes, the API interface remains unchanged, continuing to return structured information such as confidence scores, character spans, and probabilities. The team stated that releasing open weights is intended to encourage the community to experiment and build upon their ideas, helping developers supplement expensive large language model usage with smaller, faster, and cheaper purpose-built models.

Quellen:Cloudflare Blog

Forschung
Weiter →
Anmelden / Registrieren
LesenForschungRadarAnlageframework