Tag: threat intelligence

  • Researchers continue to find serious vulnerabilities in internet connected refrigerators

    As companies running refrigeration units in the U.S. and Europe recover from recent hacking incidents, threat intelligence firms have disclosed more than a dozen new serious security vulnerabilities in popular products, while others continue to track intense interest from potential threat actors in similar internet-connected devices.

    On Friday, cybersecurity firm VulnCheck published details on 14 vulnerabilities discovered earlier this year in Dixell refrigeration units, which are manufactured  by refrigeration technology firm Copeland. According to lab testing with rebuilt versions of the vendor’s firmware, each flaw would have given an attacker “root” or administrative access to the infected unit. Many of the vulnerabilities have severity scores between 8 and 9.8, and at least two are known to be under active exploitation in the wild.

    The vulnerabilities all affect Dixell and Copeland’s XWEB EVO supervision system, which is one of four known to have been affected in the October hack of refrigeration controllers in 700 supermarkets across France.

    VulnCheck security researcher Valentin Lobstein wrote that he began looking into XWEB’s cybersecurity profile after reading that an affected device from another vendor was “almost insulting” in its lapses, including setting the password of the administrative account to the current day’s date. Then he began to look at XWEB’s access controls.

    “It is worse than a weak daily code,” wrote Lobstein. “The login page runs the submitted username as a shell command before it ever checks the password.”

    Lobstein and Vulncheck notified Copeland and Dixell and helped them fix the problems before disclosing the vulnerabilities, which now have patches available. Legacy versions of the supervisory system remain exposed to potential takeover.

    Copeland confirmed to CyberScoop that certain XWEB monitoring solutions are affected. The company urged customers to keep their devices off the public internet and update to the latest patched software.

    “We continue to recommend that customers follow industry-standard cybersecurity practices, including keeping devices off the public internet and maintaining software and firmware at the most current available levels,” a Copeland spokesperson wrote in response to a request for comment. “These practices help mitigate the reported risk. We have reached out to customers to reinforce previously provided cybersecurity best practices and patching guidance, and our teams are available to support them as needed.”

    Meanwhile, XBOW researcher Max Günther set up a series of fake “honeypot” servers that mimicked the same affected vendors and models, underscoring just how quickly industrial controllers connected to the internet can attract unwanted attention.

    Günther deployed the servers online as part of a fake chain of pizza stores and indexed them with search engines such as Shodan. He also set up an online dashboard to visualize the potential real-world impact of any hacks. Within a day, the servers were getting probed by attackers, with some attempting to access and alter temperature settings.  

    “I’ve already seen hundreds of requests, everything from generic PHP2Shell-related exploit probes to actual attempts to log in to the simulated refrigeration controllers,” he wrote on LinkedIn earlier this week. “And then someone seemingly managed to log in and change the temperature of one of my virtual freezers, defrosting all the virtual pizzas inside.”

    French authorities have blamed the Iranian government for the supermarket hacks. A similar series of incidents affecting refrigeration units owned by the U.S. military are also suspected to be due to cyberattacks, according to Reuters.

    Source: CyberScoop · 2026-11-13

  • How attackers turned a Teams meeting booking into a device code phishing trap

    Attackers used a fake Microsoft Teams meeting scheduler to trick an employee at a construction company into approving a device code sign-in. They got a valid session token before Huntress’s security operations center identified the incident. Device code phishing abuses a real Microsoft sign-in flow. The attacker starts a sign-in, gets a short code back, and persuades the victim to type it into Microsoft’s genuine device login page. The victim enters the code, completes MFA … More →

    Source: Help Net Security · 2026-11-13

  • Fake Zillow pages use ClickFix NetSupport RAT to target apartment hunters

    EfficientIP Research Labs traced a ClickFix campaign that used fake Zillow apartment-review pages to install NetSupport RAT on visitors’ Windows computers. Each page showed what looked like a routine verification check. Behind it, the page quietly copied a PowerShell command to the clipboard and walked the visitor through pasting and running it. Doing that installs remote-control software that keeps its window hidden and starts back up every time the user logs in. Renters are the … More →

    Source: Help Net Security · 2026-11-12

  • Check your GitHub repos: A secret stealer hit tens of thousands of them

    A threat actor using stolen GitHub credentials has pushed a credential-stealing payload into tens of thousands of repositories since November 10. In more than 1,800 of them, the malware ran and shipped GitHub Actions secrets and cloud credentials to the attacker. Aikido spotted the campaign and named it wfx-loot. The name comes from the attacker’s own labels, “wfx” for the malware and “loot” for what it steals. Aikido counted 4,837 compromised accounts opening probe pull … More →

    Source: Help Net Security · 2026-11-12

  • Russian Turla group used new toolset to silently pilfer emails from Kazakhstan, Romanian governments

    Russian Turla group used new toolset to silently pilfer emails from Kazakhstan, Romanian governments

    Turla, a notorious cyberespionage group aligned with the Russian government, has been wielding a new, customizable toolset to compromise governments around the world over the past year, including Kazakhstan.

    The toolset was first discovered in November 2025 by cybersecurity firm ESET, which named it “Turla’s Cereal” as a play on its highly modular, interconnected and “serialized” design. It chains and exploits different legitimate functions across Microsoft Exchange, Windows, and .NET assemblies, which Microsoft has described as “the fundamental units of deployment, version control, reuse, activation scoping, and security permissions for .NET-based applications.”

    “One of the most interesting aspects of this toolset is what we did not find: external command and control infrastructure,” ESET researcher Matías Porolli wrote in the report, released Tuesday. “Instead — adding insult to injury — the victim’s compromised Exchange server is co-opted to act as the C&C infrastructure.”

    Illustration of Turla’s Cereal compromise of Microsoft Exchange servers using a modular, stealthy toolset. (Source: ESET)

    Multiple Western governments and threat intelligence firms have attributed Turla as a part of Russia’s Federal Security Service (FSB), which is tasked with gathering intelligence on foreign governments, businesses and organizations. According to MITRE, the group has compromised victims in more than 50 countries, spanning governments, militaries, private-sector companies and research organizations.  

    Porolli said the toolset was found on a compromised Exchange server used by the government of Kazakhstan on Nov. 28, 2025, where it could receive commands, execute in memory, gather intel on the organization and collect certain email messages.

    Another version found inside a Romanian government agency a month later was configured to target emails sent to or received by the Western powers — the European Union and the North Atlantic Treaty Organization — adversarial with Russia. At the time, Romanian politicians were calling for a NATO mission in the Black Sea to deter what they viewed as Russian aggression. In July, the EU announced sanctions against Russian individuals and organizations, citing a yearslong cyberespionage campaign from Turla and other Russian groups against European nations as well as the targeting of Poland’s energy grid and European businesses by Russia-aligned hacking groups.

    According to ESET, the toolset lacks many features used to identify malware, such as implants, beaconing back to command-and-control infrastructure or built-in command lists. Most executables are performed in-memory using temporary storage to avoid leaving evidence, while commands written to permanent memory are delivered via encrypted payloads.

    One component, dubbed CerealNeuron, operates as the main backdoor but does not beacon back to its operator the way many pieces of malware do. Instead, it runs on the compromised server and “passively listens for incoming web requests on paths that look like ordinary Exchange traffic.” The result is an attack that leaves no domain, IP address, hosting provider or timing patterns for defenders to find and block.

    “The Cereal toolset demonstrates that, for Turla, Exchange servers are not just mail servers — they are durable collection points, internal execution hubs, and a suitable environment for hiding sophisticated .NET tradecraft,” Porolli wrote.

    Source: CyberScoop · 2026-11-10

  • Gorbag APT group hits Ukrainian courts and city councils with self-deleting malware

    ESET has been tracking a Russia-aligned group it calls Gorbag, which has been breaking into Ukrainian organizations since at least February 2025 using spearphishing attachments and a stealer that erases itself once the data is gone. Spearphishing email message from a compromised email sender (Source: ESET) Every target ESET identified sits in Ukraine. About a quarter are law enforcement and justice bodies, another quarter are local administrations, mostly city councils in areas close to the … More →

    Source: Help Net Security · 2026-11-03

  • Unit 42 Threat Intelligence Highlights – Nov. 2, 2026

    Unit 42 Threat Intelligence Highlights – Nov. 2, 2026

    Unit 42 details recent threat intelligence, highlighting cyberespionage, financial extortion, and the rapid adoption of AI across offensive workflows.

    Source: Palo Alto Networks Unit 42 · 2026-11-02

  • Deploying AI agents securely: how Kaspersky products mitigate AI threats

    Deploying AI agents securely: how Kaspersky products mitigate AI threats

    Introduction

    AI agents and associated tooling are becoming increasingly common in corporate infrastructure. Agents can perform a range of actions with the user’s privileges, such as accessing data, running commands, and interacting with external services. This creates new security risks, especially when these tools are used without the security team’s oversight or well-designed policies.

    Detecting, tracking, and controlling AI agents is becoming one of the most pressing tasks for security teams today. We closely follow technological developments and continuously update our solutions to respond to new threats in a timely manner amid a rapidly changing technology landscape. This post describes new expertise built into Kaspersky products that helps counter the threats posed by the proliferation of AI agents. We approach this problem from several angles.

    First, you need to thoroughly understand the threat you are dealing with. To this end, we added profiles to the Kaspersky Threat Intelligence Portal that describe various AI agents and how attackers exploit them. At their core, AI agents are programs (processes) that run in the operating system on endpoints and can also launch other processes. This means that Endpoint Detection and Response solutions are among the key endpoint controls for this threat. These solutions detect the presence and launch of AI agents, track their activity, and identify potentially dangerous behavior. When needed, they also take action, such as stopping a suspicious process, blocking the activity, or isolating the host, to reduce the likelihood of an incident escalating. For this purpose, we developed specially adapted detection rules.

    You can use Kaspersky Endpoint Security, now also available as Kaspersky Next, to control and restrict the launch of AI agents. This solution uses two components to detect AI agents and control how they are used. Application Control categorizes the application processes launched on endpoints, and Web Control manages access to specific categories of web resources for users on endpoints.

    Finally, even harmless AI agents can contain malicious instructions (skills), such as those downloaded from unsafe external sources. Kaspersky Scan Engine analyzes installed applications to detect these threats and also checks LLM files for malicious code. Let’s take a closer look at these solutions and technologies.

    Tools from Anthropic and OpenAI take the top spots in the September 2026 ranking of AI agents by popularity among Kaspersky users. This list is based on telemetry from Kaspersky solutions. It shows the number of users who had the relevant AI vendors’ products installed at the time of the study.

    # AI product
    1 Claude
    2 Claude Code
    3 Codex
    4 OpenCode
    5 Zed
    6 Wispr Flow
    7 LM Studio
    8 ZCode
    9 Chatbox
    10 Cherry Studio

    The data shows that agentic systems, especially AI agents for software development, are the most popular AI applications. The TOP 10 also includes an application for running large language models locally (LM Studio) and a voice note-taking app (Wispr Flow).

    According to open sources, these are the most widely used AI services in 2026:

    # AI service
    1 ChatGPT
    2 Google Gemini
    3 Claude
    4 Grammarly
    5 DeepSeek

    While analyzing the most popular and widely used apps, our experts also noticed a sharp rise in vulnerable versions of AI-related software and services. From 2025 to date, more than 2500 vulnerabilities have been published:

    Number of published vulnerabilities in LLMs, AI tools, and plugins with similar functionality, 2025–2026 (download)

    * Data for previous quarters was updated and may differ slightly from previously published data.

    Application Control and Web Control

    To enforce the organization’s security policy for AI agents and other AI applications on the corporate network, Kaspersky products offer application control based on KL categories. These categories classify installed software and give you granular control over which approved applications can run in the organization.

    Application Control analyzes the processes launched on endpoints, tracking which AI agents are running in corporate systems at any given moment, on which hosts, and under which accounts. Application Control also shows how long a given program has been in use.

    This makes it easier for the Kaspersky Security Center (KSC) administrator to control applications. Administrators can use KL categories to allow or block AI agents inside the company for specific groups of employees.

    Here is what this functionality looks like to KSC administrators:

    KL categories available when configuring Application Control

    KL categories available when configuring Application Control

    For details on how to configure Application Control in KSC, follow this link.

    In Kaspersky Endpoint Security (KES), Application Control can operate in two modes:

    • Denylist. In this mode, Application Control lets users run any applications except those blocked by Application Control rules. This is the default mode.
    • Allowlist. In this mode, Application Control blocks users from running any applications except those explicitly allowed by Application Control rules.

    Below are the steps to configure Application Control to block AI tools.

    Configuring Application Control for the AI Tools category in KES
    Configuring Application Control for the AI Tools category in KES

    Configuring Application Control for the AI Tools category in KES

    With this setup, when a user tries to launch an AI agent, they get a notification and the agent doesn’t start.

    KES notification about an attempt to launch an AI agent

    KES notification about an attempt to launch an AI agent

    For more on how to configure Application Control in KES, follow this link. Our public portal also lets you explore information on KL categories and the applications that fall under them, in particular details on how AI agents are categorized and how popular they are.

    AI Tools KL category

    AI Tools KL category

    The View applications drop-down list shows products for a specific vendor.

    Similarly, Web Control lets you manage user access to web resources. If a user tries to open a denylisted website, KES blocks access and shows a warning.

    KES notification about an attempt to access a prohibited web resource

    KES notification about an attempt to access a prohibited web resource

    When configuring access, the administrator can block websites that provide AI as a service.

    Website categories

    Website categories

    For more on configuring Web Control, follow this link. The help portal also provides information on website categories that can be assigned to resources to configure access control.

    Kaspersky Endpoint Detection and Response

    To an EDR solution, an AI agent is a regular process. It has its own executable, a tree of child processes, and network communications, all of which need to be monitored for suspicious activity. An attacker can use an AI agent as an automation tool. An AI agent installed as a legitimate user tool can also be leveraged in a ClickFix attack, where it executes a malicious instruction received from an untrusted source, such as a document, web page, or email. That said, unsafe actions by an agent do not always indicate an attack. There may be no malicious intent in the chain at all. An incident can result from what looks like an ordinary instruction from a user who doesn’t fully understand the consequences of having it executed. The mere fact that an agent was launched does not reveal whether it is being used in an attack. That is why Kaspersky EDR (KEDR) uses both conventional behavioral rules and rules written and adapted to detect AI tools. The latter identify risky agent actions and settings, and help determine which AI tool was involved in suspicious activity.

    Conventional KEDR rules detect the vast majority of familiar malicious techniques, including when performed by an AI agent. A suspicious PowerShell launch, persistence via Task Scheduler, or an attempt to steal credentials leaves clear, identifiable traces. These traces look the same no matter what initiated the actions. The rules analyze launch parameters, process relationships, affected files, network activity, and other telemetry events.

    For example, in a recent Armored Likho campaign, we found signs that AI had been used to create loader and dropper samples, which were later compiled with NSIS (Nullsoft Scriptable Install System). The key telltale artifacts were icons in the scripts and excessive comments on every function, which is uncharacteristic of human-written code. In addition, the group continues to generate new modules for its BusySnake Stealer and BusySnake RAT samples. For example, the attackers used AI to develop a module that runs multiple checks for virtual environment artifacts and calculates a score. Depending on the score, the sample either runs or exits with code 0. Even though the initial access samples, payloads, and their modules were AI-generated, the commands they execute via rundll32 and PowerShell are detected by the shell_creation_by_rundll32 and suspicious_powershell_cmd_or_script_spawning rules.

    So, for detecting an attack like this, it is not important who wrote the loader, the payload, or its modules: they are given away by the commands they execute, process relationships, and other traces of activity in the system. AI can be involved both in preparing the code and in carrying out the attack directly on the device.

    In the latter case, the attacker uses the agent to carry out their tasks and lets it choose and run the required commands within the privileges it has. For effective protection, it is critical to link suspicious actions back to the AI tool and the conditions under which it operates. In KEDR, several specialized rules handle this task.

    We have created separate rules for popular AI agents, ai_agent_*_access_to_sensitive_file_**, where * is the tool name and ** is the operating system. They generate alerts when an agent accesses files that contain credentials, tokens, or keys.

    The ai_agent_dangerous_execution_mode rule detects agents launched with auto-approval of all actions (so-called YOLO mode) or with the sandbox disabled. These settings do not indicate an attack on their own, but they let the agent perform dangerous actions without user confirmation.

    ai_agent_dangerous_execution_mode

    The suspicious_mcp_server_artifact rule triggers when MCP server scripts are created or modified in hidden, temporary, or cache directories. Attackers can place an MCP server in these locations to quietly connect it to the agent: through the MCP server, they can pass instructions to the agent, call third-party tools, and access the user’s data.

    suspicious_mcp_server_artifact

    The llm_api_access_by_unusual_apps rule generates an alert when an application on Windows, Linux, or macOS connects to the API of a known external LLM service, unless this activity falls under predefined exclusions. This helps spot model access by applications that do not normally behave this way.

    llm_api_access_by_unusual_apps

    Some Kaspersky EDR rules tag events for investigation but do not generate alerts. For example, the ai_agent_**_execution rules flag launches of known agents on Windows, Linux, and macOS. The local_ai_model_artifact rule records the creation or modification of AI model files in typical application, runtime, and cache directories. These events reveal AI tools on the device, including tools that run on local models and never call an external API.

    local_ai_model_artifact

    Kaspersky Threat Intelligence Portal

    AI agent profiles

    The Kaspersky Threat Intelligence Portal offers a large number of software profiles, including profiles of AI agents. You can sort them by the ai_ prefix:

    AI agent profiles on Kaspersky TIP

    AI agent profiles on Kaspersky TIP

    The profile of an AI agent such as Claude Desktop includes a detailed description of the software, the privilege level required to run it, supported platforms, and threat actor groups known to use it. It also lists tactics and techniques mapped to the MITRE ATT&CK framework, with descriptions of the procedures the tool can be used for.

    Claude profile on Kaspersky TIP

    Claude profile on Kaspersky TIP

    The description also lists ways to detect the software through standard system auditing mechanisms:

    • Windows: events from standard audit logs and Sysmon events
    • Linux: syscall audit events and Sysmon events
    • Network auditing: a set of protocols and the traffic generated by the software

    The detection section lists the main artifacts the software leaves in the system: command lines, possible launch parameters, names of the services and scheduled tasks it creates, and the key network artifacts.

    Detection section in the Claude profile

    Detection section in the Claude profile

    Hunt Hub

    In December 2025, the Kaspersky Threat Intelligence Portal added Hunt Hub (HH), a repository of detection rules. This is a unique Kaspersky project, and we developed it in response to growing market demand.

    This functionality is available in the Threat Landscape section of the portal. It gives analysts access to detection rules: their descriptions and their mapping to MITRE ATT&CK tactics and techniques, as well as to the associated cybercriminal groups.

    In the Hunt Hub section, customers can explore the detection logic of EDR, NDR, and NGFW products, including the logic for detecting AI agents.

    Rules in the Hunt Hub repository

    Rules in the Hunt Hub repository

    The rule card provides:

    • Detailed description
    • Rule’s severity level, confidence level, and alert format
    • Detection tips
    • Description of possible false positives
    • Platforms the rule can run on
    • Tactics, techniques, and sub-techniques covered by the rule
    • Groups that use the technique covered by the rule
    • Detection logic that shows what exactly triggers the rule
    Detection rule card in Hunt Hub

    Detection rule card in Hunt Hub

    Kaspersky Scan Engine

    Skills are a key component of the AI agent ecosystem. They’re prewritten sets of natural-language instructions that extend agent functionality. We previously covered the risks that malicious skills pose to agent users. A skill can require the usage of additional programs and services, come with helper scripts (for example, written in Python), or contain a malicious command embedded right in the instruction text. This means that adding skills to an originally harmless AI agent opens up several new ways for malicious code to enter the system. To prevent this, any skills obtained from external sources must be scanned. Kaspersky Scan Engine is well suited for this task. This is a cyberthreat detection and response solution that seamlessly integrates with various applications. It can detect malicious code in agent skills, associated scripts, and in files generated by running agents.

    Detection of a malicious agent skill in Kaspersky Scan Engine

    Detection of a malicious agent skill in Kaspersky Scan Engine

    Trained LLMs come in many formats. Some of them (PTH, PT, PKL, KERS, and others) also store parameters and weights (training datasets). These files can also contain malicious code, so it’s critical to scan them before running and using them. Kaspersky Scan Engine scans potentially dangerous LLM formats for infected data. It can deserialize and analyze models to detect malicious code regardless of model size.

    Detection of an LLM with malicious code in Kaspersky Scan Engine

    Detection of an LLM with malicious code in Kaspersky Scan Engine

    Conclusion

    AI agents are rapidly making their way into corporate environments: they help employees work faster and take on a wide range of tasks, but they also open up new opportunities for attackers. To take advantage of this technology without compromising security, organizations need to build multi-layered protection and minimize risks. A range of Kaspersky solutions can help with this:

    • Kaspersky TIP keeps you up to date on current scenarios in which attackers use AI agents, and its Hunt Hub section provides rules for detecting suspicious AI agent activity.
    • Kaspersky EDR detects AI agents in the infrastructure and monitors their activity on endpoints. If it detects potentially dangerous actions, the product can log the event, notify the SOC, and take response actions, such as stopping the process or isolating the host.
    • Application Control in Kaspersky products can fully restrict the use of AI agents within the company by using application categorization. The Web Control component can restrict access to AIaaS web resources.
    • Kaspersky Scan Engine can be integrated into various company processes to detect malicious code in any files, including AI agent skills and LLMs.

    When companies combine the tools described above in a comprehensive approach, they can adopt AI agents in an informed way: with an understanding of the associated risks and effective means of minimizing them.

    Source: Securelist (Kaspersky GReAT) · 2026-10-26

  • Preparing for 2027: Five Trends Shaping Enterprise Threat Intelligence

    In the first half of 2026, Flashpoint tracked more than 22 million threat actor posts discussing, sharing, or advertising AI toolkits for criminal deployment. The figure reflects AI’s growing presence across the cybercriminal underground, where adversaries are using new capabilities to accelerate attacks and develop malicious tooling with fewer resources.

    For enterprise defenders, these developments are adding pressure to threat intelligence programs already managing high alert volumes, limited analyst capacity, and expanding responsibilities.

    During Flashpoint’s recent webinar, we examined the evolving threat landscape alongside findings from Flashpoint’s Global Threat Intelligence Report: 2026 Midyear Edition and new enterprise threat intelligence research.

    Missed the live webinar? We’ve rounded up the key takeaways below, and the full session is now available to watch on demand.

    AI Is Changing the Economics and Speed of Cybercrime

    AI is helping threat actors develop capabilities and execute attacks faster, reducing the time and expertise required for activities that previously demanded greater resources.

    Several developments illustrate the broader shift in cybercrime economics and attack velocity:

    • Initial access costs have declined by approximately 69%, reflecting the continued commoditization of access to compromised environments.
    • Attackers published 637 malicious package versions in just 22 minutes during a software supply chain compromise.
    • Nearly one in five vulnerabilities disclosed during the first half of this year had public or functional exploit code available, narrowing the window for defenders to address exposed systems.

    AI is primarily accelerating established techniques, particularly during the early stages of the attack chain, including reconnaissance, social engineering, vulnerability discovery, and exploitation.

    For defenders, this creates an opportunity to identify and disrupt malicious activity during its preparation stages. However, it also raises expectations around how quickly intelligence teams can recognize emerging threats, prioritize relevant findings, and act before an attack progresses.

    AI Is Changing How Cybercriminals Develop Tools and Share Knowledge

    AI is also changing how threat actors acquire the skills and capabilities needed to carry out attacks, creating new challenges for intelligence collection.

    Historically, underground communities enabled cybercriminals to collaborate, exchange expertise, and obtain specialized services. Increasingly, threat actors can use AI to troubleshoot code, develop malicious tooling, and learn unfamiliar techniques independently, reducing their reliance on public collaboration.

    “No longer do they need a community to build up their skills like they previously had. So we’ll see less of the development, and what we do see is a finished tool showing up for sale.”

    Ian GrayVP of Intelligence, Flashpoint

    Reduced activity in underground communities does not necessarily mean cybercriminal activity is declining. While forums, encrypted messaging platforms, and other illicit communities remain important intelligence sources, collection strategies must account for changes in how and where adversaries develop and distribute their capabilities.

    Threat Intelligence Teams Are Struggling to Keep Up with Growing Demands

    As adversaries accelerate their operations, enterprise threat intelligence teams are contending with growing workloads and limited resources.

    Independent research commissioned by Flashpoint surveying threat intelligence budget owners and influencers at large North American enterprises identified several leading operational challenges:

    • 65% cited alert noise and false positives.
    • 55% identified analyst bandwidth and effectiveness.
    • 50% pointed to the evolving threat landscape.
    • 50% cited tool integration and interoperability challenges.

    Note: Respondents could select up to three challenges.

    High alert volumes, disconnected systems, and manual investigations consume analyst time that could otherwise be spent addressing emerging threats.

    As one healthcare threat intelligence leader explained:

    “Good analysts take time to develop and train, and we can’t hire our way out of that problem.”

    These challenges are prompting organizations to examine how they can improve existing workflows, reduce repetitive investigations, and make better use of analyst expertise.

    Threat Intelligence Budgets Are Growing, with AI Threats Leading Investment Priorities

    Despite operational pressures, organizations are continuing to invest in threat intelligence.

    Flashpoint’s research found that 50% of respondents expect their threat intelligence budgets to increase over the next 12 months, including 35% anticipating increases of at least 10%. Another 40% expect budgets to remain essentially flat, while 0% anticipate a decrease.

    AI-related threats emerged as the leading priority for expanded intelligence coverage, particularly:

    • Deepfakes and synthetic media, including their use in impersonation, fraud, and social engineering.
    • AI-accelerated vulnerability exploitation, as adversaries identify and exploit weaknesses more quickly.
    • Emerging AI-enabled attack vectors, including changes in threat actor tactics, techniques, and procedures.

    Organizations are also investing in additional intelligence feeds, expanded security use cases, and further development of their intelligence programs.

    These priorities reinforce the importance of translating AI-related threats into specific intelligence requirements aligned with organizational risk.

    Agentic AI Adoption Is Underway, but Trust and Measurable Value Remain Essential

    Alongside investments in AI-related threat coverage, organizations are exploring how agentic AI can improve their own intelligence operations.

    Flashpoint’s research found that:

    • 25% are already using agentic AI in production.
    • 20% are piloting agentic AI or conducting proofs of concept.
    • 35% are planning adoption within the next 12 to 24 months.
    • 20% are taking a wait-and-see approach.

    Early implementations focus primarily on information retrieval, alert prioritization, contextual enrichment, intelligence platform queries, and MITRE ATT&CK mapping.

    Organizations remain more cautious about granting agents autonomy over consequential actions, such as blocking IP addresses or changing security controls.

    One research participant captured the concern:

    “An agent that’s confidently wrong is worse than one that’s slow.”

    Accuracy, data privacy, auditability, predictable costs, and human oversight remain central considerations. Organizations also expect AI investments to demonstrate measurable value through time savings, improved efficiency, and faster response.

    “We’re out of the phase of treating AI as inherently good and giving it a blank check. Now, it’s about figuring out how to make it work within existing teams, workflows, and priority intelligence requirements.”

    Joe Sawyer
    Chief Market Officer, Flashpoint

    Preparing Your Threat Intelligence Strategy for 2027

    As organizations prepare for 2027, four priorities can help guide threat intelligence planning:

    1. Plan for threats you cannot readily observe. Identify potential gaps in intelligence collection and examine emerging attack methods, including weaknesses in internal security processes.
    2. Prepare for machine-speed attacks. Evaluate detection, prioritization, and response capabilities against increasingly compressed attack timelines.
    3. Turn AI threats into actionable intelligence requirements. Map emerging techniques to relevant adversaries, established frameworks, defensive controls, and business risks.
    4. Use agentic AI where it can extend analyst capacity. Prioritize repeatable workflows that deliver measurable value while maintaining appropriate data controls and human oversight.

    Watch 22 Million Reasons to Rethink Your 2027 Threat Intelligence Strategy for a deeper look at the cybercriminal underground, enterprise threat intelligence investment trends, and practical considerations for agentic AI adoption.

    See Flashpoint in Action

    Source: Flashpoint · 2026-10-22

  • Top 5 Initial Access Threat Vectors Observed by Unit 42 in September 2026

    Top 5 Initial Access Threat Vectors Observed by Unit 42 in September 2026

    Unit 42 details the top initial access vectors adversaries use to breach organizations, led by edge exploits, credential abuse and phishing

    Source: Palo Alto Networks Unit 42 · 2026-10-16