Author: admin

  • The Browser Is Now the Battleground: How Chrome Zero-Days Are Targeting Enterprise Users in 2026

    The Browser Is Now the Battleground: How Chrome Zero-Days Are Targeting Enterprise Users in 2026

    Your employees spend more time in Chrome than in any other application. Every SaaS tool, every cloud dashboard, every internal portal runs through the browser. And in March 2026, Google confirmed that two critical Chrome zero-days — CVE-2026-3909 and CVE-2026-3910 — were actively being exploited in the wild before the patch was available.

    The browser has quietly become the most dangerous attack surface in enterprise environments. It runs on every machine. It executes untrusted code constantly. It is the gateway to every cloud application your organization uses. And most security teams do not have meaningful visibility into what happens inside it.

    This post explains why Chrome zero-day exploits have become so valuable, how CVE-2026-3909 and CVE-2026-3910 are weaponized, and what enterprise security teams should do right now to reduce browser-based risk.

    What Are CVE-2026-3909 and CVE-2026-3910?

    CVE-2026-3910 is a type confusion vulnerability in Chrome’s V8 JavaScript and WebAssembly engine. Type confusion occurs when code handles memory allocated for one type of object as if it were a different type, creating conditions for arbitrary read/write operations in memory. In practical terms, a malicious webpage or ad network can trigger CVE-2026-3910 to achieve remote code execution within the Chrome renderer process.

    CVE-2026-3909 is a vulnerability in Chrome’s Skia rendering engine — the graphics library that processes visual elements across the browser. This vulnerability is typically chained with CVE-2026-3910: once the V8 flaw achieves code execution in the renderer, CVE-2026-3909 provides a sandbox escape path, allowing the attacker to break out of Chrome’s security sandbox and reach the underlying operating system.

    Both vulnerabilities were patched in Chrome 134.0.6998.117/118, released March 10, 2026. Both were confirmed with in-the-wild exploitation at the time of disclosure.

    Why Is the Browser Your Most Dangerous Attack Surface?

    The Browser Runs Untrusted Code Constantly

    Every webpage your employees visit executes JavaScript in the browser context. Unlike a desktop application that runs static, reviewed code, the browser is designed to run code from millions of unvetted sources. This is fundamentally different from any other application in your environment, and it is the core reason browsers are so attractive to exploit kit developers.

    A compromised ad network, a watering hole attack on an industry publication, a malicious script injected into a legitimate third-party service — all of these can deliver exploit payloads to your users without any download, attachment, or click-through required. The browser’s trust model was designed for the consumer web and is not compatible with enterprise security requirements.

    The SaaS Attack Surface Amplifier

    81% of corporate data now lives in SaaS applications accessed via browser, according to 2026 cloud security research. Compromising the browser does not just give an attacker code execution on the endpoint — it gives them authenticated access to every web application that browser has an active session with: email, file storage, project management tools, HR systems, financial platforms, and internal dashboards.

    This is why browser zero-days command extraordinary prices on dark web markets: $1 million to $3 million for a full Chrome remote code execution plus sandbox escape chain, according to Zerodium’s 2025/2026 pricing. That pricing reflects the actual value of access: one successful browser exploit can yield access to an entire organization’s cloud infrastructure without touching a single traditional endpoint.

    What Happens When Teams Don’t Solve This

    The enterprise patch lag for browser updates averages 14 days after release. Critical vulnerability exploitation begins within 4.76 days of disclosure. The gap is 9 days of structural exposure, even in organizations that take browser patching seriously.

    For organizations that treat browser updates as low-priority IT maintenance, the exposure window can stretch to weeks or months. During that window, a single visit to a compromised website delivers full compromise to any unpatched user.

    How CVE-2026-3910 Is Weaponized: The V8 Exploit Chain

    For security teams who need to understand the mechanics to inform detection strategy, here is how a V8 type confusion exploit typically operates:

    • Trigger the type confusion. Malicious JavaScript manipulates the V8 engine’s object type tracking through a carefully crafted sequence of operations.
    • Achieve arbitrary read/write. The type confusion creates a “confused” object whose size metadata is incorrect, allowing the attacker to read from and write to arbitrary memory locations.
    • Bypass ASLR. The attacker uses the arbitrary read capability to leak memory addresses, defeating Address Space Layout Randomization.
    • Shellcode execution. With ASLR defeated and write primitives established, the attacker overwrites a function pointer to redirect execution to shellcode.
    • Sandbox escape via CVE-2026-3909. Chrome’s renderer sandbox prevents direct OS access. CVE-2026-3909 provides the escape path via a Skia rendering flaw that reaches GPU process memory and subsequently the OS kernel.

    Old Way vs. New Way: Browser Security Posture

    Old Approach Modern Approach
    Patch browsers on monthly IT cycle Force-update browsers within 24 hours of critical patch
    Block known malicious domains Add browser isolation for high-risk browsing sessions
    Rely on antivirus for post-exploit detection Deploy EDR with behavioral heuristics for renderer process anomalies
    Hope employees don’t visit malicious sites Assume users will visit compromised sites and build detection around post-exploit behavior
    No visibility into browser process activity EDR monitoring of Chrome renderer, GPU process, and child process spawning
    Single-factor SaaS authentication MFA on every SaaS app to limit post-exploit session hijacking

    How Peris.ai Addresses the Browser Threat

    Peris.ai’s integrated platform addresses browser threats across three layers:

    EDR is the primary detection layer for browser exploit chains. Peris.ai’s EDR monitors Chrome renderer process behavior in real time: heap spray activity, unusual memory allocation patterns, child process spawning from the browser context (a classic post-exploitation indicator), and network connections initiated by the renderer process to unexpected destinations. These behavioral signals are detectable without CVE signatures and fire whether the exploit is known or novel.

    INDRA CTI tracks browser exploit kit activity across the threat landscape. When new Chrome zero-day exploitation campaigns emerge, INDRA CTI provides IOCs for the C2 infrastructure, the exploit delivery domains, and the post-exploitation tooling.

    BrahmaFusion automates the response. When EDR detects a compromised browser session, BrahmaFusion’s AI Playbook Builder can automatically isolate the affected endpoint, revoke active SaaS sessions via integrated identity provider APIs, notify the security team, and open an incident case in the Peris.ai IRP, all before an analyst has completed reviewing the first alert.

    Enterprise Browser Security Hardening: A Practical Checklist

    • Force-update Chrome immediately. Patch to 134.0.6998.117 or later. Do not wait for your standard patch cycle for CVSS 8.0+ browser vulnerabilities.
    • Enable Chrome’s Enhanced Safe Browsing. This provides real-time URL checking against Google’s threat databases and is a zero-cost hardening measure.
    • Restrict browser extensions. Enforce allowlisting of approved extensions via Google Workspace or Microsoft Intune policies. Unauthorized extensions are a parallel compromise vector.
    • Monitor child processes spawned from Chrome. PowerShell, CMD, or WScript spawned as a child of the Chrome renderer process is a near-certain indicator of successful exploitation.
    • Deploy behavioral EDR on all endpoints. Signature-based detection cannot catch novel exploit chains. Behavioral heuristics tied to the renderer process are the effective detection layer.
    • Implement MFA on all SaaS applications. Post-exploitation session hijacking is the most common browser exploit follow-on. MFA limits the blast radius of a compromised browser session.
    • Evaluate browser isolation. Remote browser isolation (RBI) eliminates browser zero-day risk by running browser code in an isolated cloud environment. Adoption is still under 12% of enterprises, representing a significant untapped risk reduction opportunity.

    Benefits at a Glance

    Capability Outcome
    EDR renderer process monitoring Detects exploit chains via behavioral heuristics, not signatures
    INDRA CTI browser exploit intelligence IOC context for Chrome exploit campaigns
    BrahmaFusion automated isolation Endpoint contained and SaaS sessions revoked within minutes
    Peris.ai IRP case management Structured investigation for post-exploit forensics
    47% cost savings Measured across Peris.ai client portfolio for contained incidents

    Conclusion

    CVE-2026-3909 and CVE-2026-3910 are a reminder that the browser is not just an application — it is the primary attack surface for the modern enterprise. With 81% of corporate data in SaaS apps and every employee spending most of their day in Chrome, the browser is the highest-value target in your environment.

    Patch immediately. Deploy behavioral EDR. And accept that the question is not whether your users will encounter browser exploit attempts — it is whether your detection stack will catch what happens after one succeeds.

    Explore how Peris.ai’s EDR and BrahmaFusion protect enterprise endpoints from browser-based threats. Visit peris.ai/blog for more enterprise security insights, or explore the full platform at peris.ai.

    Frequently Asked Questions

    What are CVE-2026-3909 and CVE-2026-3910?

    CVE-2026-3910 is a V8 JavaScript engine type confusion vulnerability enabling remote code execution in Chrome. CVE-2026-3909 is a Skia rendering engine flaw used to escape Chrome’s sandbox. Both were exploited in the wild and patched in Chrome 134.0.6998.117 in March 2026.

    Why are Chrome zero-days so expensive on dark web markets?

    A full Chrome RCE plus sandbox escape chain is valued at $1M to $3M because it grants code execution on the victim’s machine and authenticated access to all open browser sessions, effectively bypassing SaaS authentication for every cloud app the user is logged into.

    How can EDR detect Chrome exploit chains without a CVE signature?

    Behavioral EDR monitors Chrome’s renderer process for heap spray activity, unusual memory allocations, unexpected child process spawning (e.g., PowerShell from Chrome), and outbound network connections from the renderer, all of which are indicators of post-exploitation regardless of the specific vulnerability exploited.

    What is the enterprise browser patch lag in 2026?

    Enterprises take an average of 14 days to deploy browser patches after release. Since exploitation of disclosed critical vulnerabilities begins within 4.76 days, organizations face approximately 9 days of structural exposure even with active patch programs.

    What is remote browser isolation (RBI) and how does it help?

    Remote browser isolation runs browser execution in an isolated cloud or server environment, sending only a visual stream to the user’s endpoint. This eliminates local code execution entirely, making browser zero-day exploits ineffective. Adoption remains below 12% of enterprises as of 2026.

  • 2026 Is the Year AI Stopped Assisting Attackers and Started Leading Them

    2026 Is the Year AI Stopped Assisting Attackers and Started Leading Them

    For years, the cybersecurity industry described AI as a tool that attackers might one day use to accelerate their campaigns. That future arrived in 2026 and it arrived faster and more completely than most threat models anticipated.

    CrowdStrike’s 2026 Global Threat Report documents an 89% year-over-year surge in AI-enabled adversarial activity. New malware families like PROMPTFLUX, PROMPTSTEAL, and PROMPTLOCK don’t just use AI to choose their targets or craft phishing emails. They embed large language models directly into their execution runtime, generating obfuscated exploit code on demand, adapting to the specific environment they’re operating in, and producing new attack variants that have never existed in any threat database before.

    This is the inflection point the industry has been warning about. The question is whether your defense architecture was built for it.

    What Is AI-Powered Cyberattack Capability in 2026?

    AI-powered cyberattacks in 2026 go far beyond automated phishing. The term now describes attacks where AI actively participates in offensive decision-making: selecting targets, generating payloads, adapting to defensive responses, and evading detection in real time. Three tiers of capability are now in active use:

    Tier 1: AI-assisted attacks — Human operators use AI to accelerate specific tasks (phishing content generation, code reuse, target profiling). This was the dominant model in 2024-2025.

    Tier 2: AI-augmented attacks — AI handles entire phases of the attack chain autonomously while humans supervise. Reconnaissance, initial payload generation, and vulnerability matching now run at machine speed.

    Tier 3: Agentic AI attacks — The malware itself contains an AI model that makes operational decisions without human input. PROMPTFLUX, PROMPTSTEAL, and PROMPTLOCK represent this tier. They are not AI-assisted; they are AI-led.

    The Malware Families Rewriting the Rules

    Three newly documented malware families define the 2026 threat landscape:

    PROMPTFLUX generates entirely novel obfuscated code at runtime. Each execution produces unique code that has never existed before, bypassing signature-based and hash-based detection entirely. There is no static indicator of compromise to match against.

    PROMPTSTEAL uses embedded LLM capability to understand the context of the environment it has accessed, identifying high-value credentials, sensitive documents, and communication patterns, and exfiltrates with surgical precision rather than bulk extraction.

    PROMPTLOCK is a ransomware variant that generates unique encryption implementations per target, making decryptor development impractical. It also uses LLM analysis to identify the most operationally damaging files to encrypt first.

    The precursors to these families are already documented: MalTerminal, the earliest known GPT-4-powered malware generating ransomware and reverse-shell code at runtime. LAMEHUG, which uses live LLM interactions to generate system commands on demand rather than using a fixed command set.

    The Speed Advantage Has Shifted

    The 89% increase in AI-enabled attacks is not just a volume story. It’s a speed story. AI can analyze newly published patches the moment they’re released and generate working exploit code in minutes. 61% of new CVEs are now weaponized within 48 hours of disclosure. The time-to-exploit window with AI assistance has compressed to a single day for high-value vulnerabilities.

    Defense teams operating on weekly patching cycles or manual triage workflows are structurally misaligned with this tempo.

    The Defense Paradigm That No Longer Works

    The legacy defense model was built on a core assumption: that known-bad indicators, file hashes, IP addresses, domain names, YARA signatures, could be collected, shared, and used to block attacks before they succeeded.

    This model worked when attackers reused tools, infrastructure, and code across campaigns. It fails when:

    • Each payload is unique and generated on demand
    • C2 infrastructure rotates faster than threat intelligence feeds update
    • Exploitation occurs within hours of vulnerability disclosure
    • The malware itself adapts to the detection environment it encounters

    Signature-based detection, static vulnerability scanning, and human-speed triage are not wrong, they remain necessary, but they are no longer sufficient as the primary defensive layer.

    What Happens When Teams Don’t Adapt

    Legacy Defense Failure Mode Against AI-Led Attacks
    Signature-based AV/EDR PROMPTFLUX generates unique code per execution; no signature exists
    IOC-based threat intel Infrastructure rotates in hours; IOCs expire before distribution
    Manual SOC triage AI attacks exploit and exfiltrate before humans complete first review
    Weekly patch cycles 61% of CVEs weaponized in 48 hours; patch window exceeds exploit window
    Perimeter-only detection Agentic malware operates laterally within trusted zones

    Only Autonomous, Agentic AI Defense Can Match Autonomous, Agentic Offense

    The industry’s response to AI-led attacks cannot be faster humans. It has to be autonomous AI defense: systems that detect, analyze, and respond at machine speed, without waiting for an analyst to click approve.

    This is the core design principle behind BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform. BrahmaFusion does not wait for a human to review an alert. It ingests telemetry from EDR, XDR, NVM, and external threat intelligence simultaneously, identifies behavioral patterns that indicate AI-generated attack activity, including runtime code generation, anomalous API call sequences, and unusual LLM-style query patterns, and executes containment workflows automatically.

    INDRA CTI provides real-time threat actor attribution and campaign tracking. When a new AI-enabled malware family is documented, INDRA CTI maps its behavioral indicators to your environment’s telemetry and surfaces exposure within minutes, not days.

    Our XDR and EDR provide the multi-layer telemetry that BrahmaFusion’s AI operates on. Behavioral baselines established over time allow anomaly detection that doesn’t depend on known-bad signatures, exactly what’s needed against PROMPTFLUX-style polymorphic payloads.

    A leading financial startup using BrahmaFusion achieved 40% SOC cost savings while simultaneously improving detection coverage. The platform reduced analyst workload by 35% by automating triage, enrichment, and containment for the majority of alerts, freeing human analysts to focus on the cases that genuinely require human judgment.

    Real-World Scenario: Detecting PROMPTFLUX in a Financial Environment

    • T+0:00 — A finance employee opens a phishing PDF; PROMPTFLUX is dropped and begins LLM-based environment analysis
    • T+0:04 — EDR detects anomalous API call sequences inconsistent with any known malware family
    • T+0:05 — BrahmaFusion correlates the API pattern with behavioral indicators from INDRA CTI’s LLM malware taxonomy
    • T+0:07 — The host is automatically isolated; PROMPTFLUX’s exfiltration attempt fails
    • T+0:09 — An IRP case is created with full behavioral trace, MITRE ATT&CK mapping (T1059, T1027), and automated remediation steps
    • T+2:15 — Analyst reviews case, confirms containment, and approves host restoration

    Total analyst involvement: 4 minutes of review. Total attack window: under 10 minutes, zero exfiltration.

    Benefits of Agentic AI Defense Against AI-Led Attacks

    Benefit Outcome
    Behavioral detection independent of signatures Catches PROMPTFLUX-style polymorphic payloads
    Machine-speed automated response Containment executes before human review cycle completes
    INDRA CTI LLM malware tracking New AI malware families mapped to your environment in real time
    BrahmaFusion correlation across all layers No single telemetry source is a detection bottleneck
    40% SOC cost savings Proven in production at financial sector clients
    53% breach impact reduction Across Peris.ai customer base

    Conclusion

    The 89% surge in AI-enabled attacks documented by CrowdStrike in 2026 is not a trend line to monitor. It’s a structural shift in the threat landscape that has already outpaced the legacy defense model’s ability to respond. PROMPTFLUX, PROMPTSTEAL, and PROMPTLOCK are not hypothetical. They are in active deployment against organizations that have not yet updated their defense architecture for the era of autonomous AI offense.

    Peris.ai was built for this moment. BrahmaFusion’s agentic AI, INDRA CTI’s real-time intelligence, and our XDR and EDR telemetry layers are specifically designed to meet autonomous attacks with autonomous defense. Learn more about how Peris.ai protects organizations at machine speed: visit Peris.ai.

    FAQ

    What are AI-powered cyberattacks?

    AI-powered cyberattacks use artificial intelligence to automate or enhance offensive capabilities, including payload generation, target selection, evasion adaptation, and autonomous decision-making during an intrusion. In 2026, the most advanced variants embed LLMs directly into malware execution runtimes.

    What is PROMPTFLUX malware?

    PROMPTFLUX is a malware family that uses an embedded LLM to generate unique, obfuscated exploit code at runtime on every execution. Because each instance is unique, traditional signature-based detection cannot identify it.

    How fast are AI-generated exploits developed?

    With AI assistance, working exploits can be developed within minutes of a patch release. 61% of newly disclosed CVEs are weaponized within 48 hours, and some high-value vulnerabilities are exploited within a single day of public disclosure.

    How does agentic AI defense work?

    Agentic AI defense uses autonomous AI systems to ingest multi-source telemetry, detect behavioral anomalies that indicate attacks, and execute containment workflows automatically, without waiting for human approval. Platforms like BrahmaFusion by Peris.ai operate at machine speed to match the tempo of AI-led attacks.

    What is the difference between AI-assisted and agentic AI attacks?

    AI-assisted attacks use AI to speed up specific human-directed tasks. Agentic AI attacks embed AI into the malware itself, allowing it to make operational decisions autonomously during an intrusion, selecting targets, generating payloads, and adapting to defenses without human input.

  • When Your CFO’s Voice Isn’t Really Your CFO: The $1.1 Billion Deepfake Fraud Wave Hitting Finance

    When Your CFO’s Voice Isn’t Really Your CFO: The $1.1 Billion Deepfake Fraud Wave Hitting Finance

    Deepfake voice fraud drained $1.1 billion from US corporate accounts in 2025. In 2026, the attacks are faster, cheaper, and more convincing than ever. Here is how they work, and what finance and security leaders need to do about it.

    The call sounded exactly like the CFO. The voice, the cadence, even the slight impatience in the tone. The wire transfer instruction was specific, urgent, and entirely plausible. The finance associate on the other end of the call had no reason to question it.

    That call was a fraud. The CFO never made it. A criminal did, using a voice cloned from three seconds of publicly available audio.

    Deepfake CEO fraud, also called vishing executive impersonation, is the fastest-growing financial crime targeting enterprises in 2026. This post explains how it works, what the data says, and how organisations can defend against it before the next fraudulent wire instruction lands in their inbox.

    What Is Deepfake CEO Fraud?

    Deepfake CEO fraud is a form of business email compromise (BEC) evolved to the voice channel. Attackers use AI voice synthesis tools to clone the voice of a senior executive, then use the synthetic voice in real-time phone calls or audio messages to authorise fraudulent wire transfers, request credential resets, or instruct employees to bypass security controls. The attack exploits the inherent trust that employees place in the voices of their leadership.

    The Scale of the Problem: $1.1 Billion and Rising

    The numbers attached to deepfake voice fraud in 2025 and 2026 are not projections. They are documented losses:

    • Deepfake voice attacks drained $1.1 billion from US corporate accounts in 2025, tripling the prior year’s figure of $360 million
    • 243% surge in deepfake voice attacks over the past year
    • Average loss per deepfake vishing case: approximately $600,000
    • 10% or more of financial institutions have suffered deepfake vishing attacks exceeding $1 million per incident
    • Deloitte projects the trajectory of deepfake fraud losses reaching $40 billion in the coming years
    • A Swiss businessman was defrauded of several million Swiss francs via voice cloning in January 2026

    The technology enabling these attacks is not expensive or restricted. A convincing voice clone can now be generated from as little as three seconds of audio. Every earnings call, conference keynote, podcast interview, and media appearance that a finance executive has ever recorded is raw training data for criminals.

    How Attackers Execute a Deepfake Voice Fraud

    Step 1: Target Selection and Audio Harvesting

    Attackers identify a target organisation and select an executive whose voice is publicly available. CFOs, CEOs, and General Counsels are the most common targets because they have authority to authorise financial transactions. Public audio sources include YouTube interviews, investor calls, conference recordings, and podcasts.

    Step 2: Voice Synthesis

    Using commercial or criminal AI voice tools, attackers generate a synthetic voice model capable of producing real-time speech in the target’s voice. Criminal AI toolkits purpose-built for fraud, including tools tracked by INDRA CTI, have removed the technical barriers that previously required specialist knowledge.

    Step 3: The Call

    The attacker calls a finance associate, accounts payable team member, or IT help desk. The synthetic voice delivers an urgent instruction: a wire transfer to a new account, an emergency credential reset, or a request to bypass normal approval workflows due to time pressure. The social engineering is often reinforced by a follow-up email from a spoofed or compromised address.

    Step 4: Covering Tracks

    Once the transfer is made or credentials are compromised, the attacker moves quickly. Funds are often through multiple accounts within hours. By the time the real executive is informed, recovery is typically impossible.

    What Happens When Organisations Are Unprepared?

    Organisations without voice verification protocols and deepfake detection capabilities face several compounding risks:

    • Finance teams have no way to distinguish a legitimate executive call from a synthetic one in real time
    • Standard callback verification can be defeated if the attacker has also compromised the executive’s phone number or email
    • HR teams receive fraudulent payroll diversion requests using the same technique
    • Reputational damage extends beyond the financial loss, particularly for publicly listed companies

    Before vs. After: Deepfake Defence Maturity

    Capability Unprepared Organisation Prepared Organisation
    Voice verification None, relies on caller recognition Multi-factor verbal authentication codes
    Wire transfer approval Single phone authorisation accepted Out-of-band dual approval required
    Executive audio monitoring Not tracked Alerts on new public executive audio
    Incident response for fraud Ad-hoc, no playbook Peris.ai IRP with dedicated BEC/fraud workflow
    Threat intelligence Generic advisories INDRA CTI tracks criminal AI toolkits in real time

    How Peris.ai Protects Against Deepfake Executive Fraud

    INDRA CTI monitors the criminal AI toolkit ecosystem, including voice synthesis tools and the marketplaces where they are sold and leased. When new deepfake voice fraud toolkits targeting finance executives are identified, INDRA CTI surfaces intelligence on their capabilities, infrastructure, and indicators of compromise to your security team before your organisation becomes a target.

    BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform, can be configured to detect the specific combination of signals that precede a deepfake vishing attack: anomalous wire transfer requests in email chains that reference a phone call as authorisation, executive name mentions combined with financial transaction keywords, and unusual patterns in help desk credential reset requests. When these signals appear together, BrahmaFusion triggers automated review workflows before a transfer is approved.

    Peris.ai IRP provides the incident response framework for organisations that have already been targeted. When a deepfake fraud incident is suspected, Peris.ai IRP opens a structured case with a pre-built workflow covering evidence collection, financial institution notification, regulatory reporting requirements, and post-incident controls review.

    Scenario: The $2.4 Million Phone Call

    A mid-size fintech company receives a call from the CFO’s number at 4:45pm on a Friday. The voice instructs the accounts payable manager to release a $2.4 million payment to a new vendor account before close of business, citing a signed contract that will be emailed shortly.

    Without deepfake defence controls, the transfer is approved.

    With Peris.ai controls in place:

    • BrahmaFusion detects the pattern: Friday afternoon wire request + phone authorisation + new vendor account, and flags it for secondary review
    • INDRA CTI confirms that a criminal voice synthesis toolkit has been actively targeting fintech CFOs in the region that week
    • The finance manager receives an automated alert requiring out-of-band confirmation via the company’s verified internal messaging system
    • The real CFO is contacted. The fraud is stopped. The $2.4 million stays where it belongs.

    Benefits at a Glance

    Benefit Outcome
    INDRA CTI criminal AI monitoring Early warning on deepfake toolkits targeting your sector
    BrahmaFusion pattern detection Automated flag on high-risk transaction request combinations
    Peris.ai IRP fraud workflow Structured response when deepfake incidents occur
    Vendor and partner notification BrahmaFusion playbooks cover third-party fraud scenarios

    Final Thought

    Every earnings call your CFO has ever recorded is a training dataset. Every investor presentation is source material. The voice that your finance team trusts most is now replicable from a few seconds of audio, and the tools to do it are available to criminals on underground markets today.

    The organisations that survive this threat are not those with better voice recognition. They are those with better processes: verification controls, threat intelligence, and incident response capabilities that assume synthetic voices are a real and present risk.

    Platforms like BrahmaFusion by Peris.ai, combined with INDRA CTI’s real-time monitoring of criminal AI toolkits, give lean security teams the intelligence and automation to stop these attacks before the wire goes out. Don’t wait for a breach to take action. Secure your organisation today. Stay Secure with Peris.ai.

    Frequently Asked Questions

    What is deepfake CEO fraud?

    Deepfake CEO fraud is a type of business email compromise attack where criminals use AI voice synthesis to clone an executive’s voice and make fraudulent phone calls authorising wire transfers or credential changes. A convincing voice clone can be created from as little as 3 seconds of publicly available audio.

    How much money has been lost to deepfake voice fraud?

    Deepfake voice attacks drained $1.1 billion from US corporate accounts in 2025, tripling the prior year’s losses. The average loss per deepfake vishing case is approximately $600,000, and over 10% of financial institutions have suffered attacks exceeding $1 million per incident.

    How do attackers clone an executive’s voice?

    Attackers harvest publicly available audio from earnings calls, podcasts, conference recordings, and media interviews. Using commercial or criminal AI voice synthesis tools, they generate a real-time voice model. The process requires minimal technical skill and can be completed in hours.

    What is the best defence against deepfake voice fraud?

    Effective defence combines multi-factor out-of-band verification for financial authorisations, real-time threat intelligence on criminal AI toolkits (such as INDRA CTI), automated detection of anomalous transaction patterns (such as BrahmaFusion), and a prepared incident response workflow for when attacks occur.

    How does BrahmaFusion detect deepfake fraud attempts?

    BrahmaFusion analyses combinations of signals that correlate with deepfake fraud: wire transfer requests referencing phone authorisations, executive name mentions combined with financial transaction keywords, and unusual help desk credential reset patterns. When these signals appear together, it triggers automated secondary approval workflows before transactions are processed.

  • CVE-2026-42897: How an Unpatched Exchange XSS Becomes a Full Network Compromise

    CVE-2026-42897: How an Unpatched Exchange XSS Becomes a Full Network Compromise

    CVE-2026-42897 is an active CVSS 8.1 XSS flaw in Exchange Server with no patch. Here is your action plan.

    On May 14, 2026, Microsoft disclosed CVE-2026-42897, a cross-site scripting (XSS) vulnerability in Exchange Server 2016, 2019, and the Subscription Edition. This is not a theoretical risk. The flaw scores 8.1 on the CVSS scale, enables unauthenticated network exploitation, and Microsoft has not released a patch. The only available mitigation is the Exchange Emergency Mitigation (EM) Service workaround.

    If your organization runs on-premises Exchange, this is not a disclosure to bookmark for later. It is an active exposure to remediate today.

    What Is CVE-2026-42897?

    CVE-2026-42897 is classified as an improper neutralization of input during web page generation, a reflected or stored XSS flaw in the Exchange web interface. The attack vector is network-accessible and requires no authentication from the attacker.

    In practical terms: an attacker with network-level access to your Exchange Server can craft a malicious HTTP request, inject script into web pages served by Exchange, and use that access to steal session tokens, impersonate users, or escalate to administrative privileges.

    Key technical facts:

    • CVSS score: 8.1 (High)
    • Affected versions: Exchange Server 2016, 2019, Subscription Edition (all on-premises)
    • Attack vector: Network, unauthenticated
    • Flaw class: CWE-79, Improper Neutralization of Input During Web Page Generation (XSS)
    • Patch status: None available as of May 14, 2026
    • Available workaround: Exchange Emergency Mitigation (EM) Service

    Why On-Premises Exchange Remains the Highest-Value Target in Enterprise Networks

    Exchange Server holds email communications, calendar data, contact directories, and deep integration with Active Directory. A compromise of Exchange is, in most organizations, a compromise of the communication backbone and a gateway to lateral movement across the entire network.

    History confirms the pattern. ProxyLogon (2021) and ProxyShell (2021) were exploited within hours of disclosure and resulted in widespread ransomware deployment and persistent access.

    What Happens When Teams Do Not Act Immediately

    • Unpatched Exchange servers are indexed by Shodan and Censys within hours of a CVE disclosure
    • Session token theft via XSS enables attacker access under legitimate user credentials, bypassing perimeter controls
    • Once inside email, attackers conduct BEC campaigns, access credential-sharing threads, and harvest lateral movement intelligence
    • Dwell time on undetected Exchange compromises averaged 197 days in 2025

    How Does CVE-2026-42897 Escalate to a Full Network Compromise?

    Stage 1: Reconnaissance. The attacker scans for on-premises Exchange servers.

    Stage 2: XSS injection. A crafted HTTP request exploits the improper input neutralization. The injected script executes in the victim’s browser context.

    Stage 3: Session token theft. The script exfiltrates the victim’s authentication session token. For administrator accounts, this is immediately catastrophic.

    Stage 4: Authenticated access. Using the stolen token, the attacker impersonates the victim: reads emails, creates inbox rules for persistence, exports contact lists, probes credential threads.

    Stage 5: Lateral movement. With credentials and organizational intelligence from email, the attacker traverses the network using Exchange’s Active Directory integration as a map.

    Stage 6: Ransomware or data exfiltration. With domain-level access established, the attacker deploys ransomware, exfiltrates data for extortion, or establishes long-term persistence.

    Context: May 2026 Enterprise Infrastructure Zero-Day Wave

    CVE-2026-42897 did not arrive alone. In the same disclosure window, Microsoft disclosed CVE-2026-45585, a BitLocker bypass (CVSS 6.8). The same week confirmed active exploitation of CVE-2026-20182, a critical authentication bypass in Cisco Catalyst SD-WAN Controllers. PraisonAI’s CVE-2026-44338 (CVSS 7.3) was exploited within four hours of its disclosure, illustrating how compressed the window between disclosure and attack has become.

    Old Way vs. New Way: Exchange Security Posture

    Approach Old Way New Way
    Patch management Wait for Patch Tuesday Emergency response to zero-day disclosures
    XSS mitigation Rely on WAF rules Enable Exchange EM Service immediately
    CVE awareness Read security blogs Real-time intelligence feeds
    Detection Periodic SIEM review Continuous behavioral monitoring
    Incident response Manual ticket creation Automated playbook on Exchange anomaly
    Attack surface Periodic external scan Continuous ASM with CVE correlation

    How Peris.ai Closes the CVE-2026-42897 Gap

    BimaRed continuously scans your external attack surface, including all exposed Exchange endpoints. When CVE-2026-42897 was disclosed, BimaRed correlates your Exchange version inventory against the CVE profile and flags affected assets within hours, giving your team a prioritized remediation list before an attacker finds you.

    INDRA CTI delivers real-time zero-day intelligence feeds. When a new Exchange CVE drops, INDRA CTI alerts your SOC with indicators of compromise, known attack patterns, and the threat actor profiles most likely to exploit the flaw.

    Peris.ai IRP provides structured incident response workflow. If compromise is detected, IRP creates a unified case aggregating all related alerts, assigns investigation tasks, and tracks remediation through resolution, mapped to MITRE ATT&CK.

    XDR monitors for post-exploitation behaviors: abnormal inbox rule creation, lateral movement from Exchange-connected accounts, privilege escalation attempts, and unusual data access patterns across endpoints and cloud services.

    Use Case: Rapid Triage of CVE-2026-42897 Exposure

    A financial services firm running Exchange Server 2019 receives an INDRA CTI alert at 09:00 on May 14, 2026, tagging CVE-2026-42897 as actively researched by known threat actors. BimaRed immediately correlates the firm’s external Exchange endpoints against the CVE profile and flags three servers as potentially exposed. The security team activates the Exchange EM Service workaround across all three servers by 11:00. XDR continues monitoring for session anomalies and lateral movement through the weekend. Total response window: two hours from disclosure to mitigation deployment. No compromise detected.

    Benefits

    Benefit Outcome
    Real-time CVE intelligence Team knows about CVE-2026-42897 within minutes of disclosure
    Automated attack surface correlation Exposed Exchange assets flagged without manual scanning
    Structured incident response IRP ensures no remediation step is missed
    Continuous behavioral monitoring XDR catches post-exploitation activity that static controls miss

    Conclusion

    CVE-2026-42897 separates prepared organizations from compromised ones. There is no patch. The attack surface is large. The exploitation path is well-understood. Your response window is hours, not days.

    Peris.ai’s combination of BimaRed, INDRA CTI, XDR, and IRP gives your security team the tools to respond at machine speed. Explore the Peris.ai security operations platform at peris.ai/blog and learn how organizations across ASEAN are defending against zero-day threats before they escalate.

    FAQ

    What is CVE-2026-42897?

    CVE-2026-42897 is a CVSS 8.1 cross-site scripting vulnerability in Microsoft Exchange Server 2016, 2019, and Subscription Edition, disclosed May 14, 2026. It allows unauthenticated attackers with network access to inject malicious scripts into Exchange web pages.

    Is there a patch for CVE-2026-42897?

    As of the May 14, 2026 disclosure, no patch exists. The only available mitigation is enabling the Exchange Emergency Mitigation (EM) Service.

    Which Exchange versions are affected by CVE-2026-42897?

    Exchange Server 2016, 2019, and Subscription Edition (all on-premises). Exchange Online (Microsoft 365) is not affected.

    How quickly can attackers exploit CVE-2026-42897?

    Based on the pattern of recent enterprise zero-days, exploitation attempts typically begin within hours of public disclosure. PraisonAI’s CVE-2026-44338 was exploited within four hours of its disclosure in the same timeframe.

    How does Peris.ai help with Exchange zero-day response?

    BimaRed identifies exposed Exchange endpoints and correlates them with CVE profiles. INDRA CTI delivers real-time zero-day alerts. XDR monitors post-exploitation behavior. IRP manages the incident response workflow from detection through remediation.

  • When the Phishing Email Knows Your CFO’s Writing Style: The AI-BEC Threat Banks Cannot Ignore

    When the Phishing Email Knows Your CFO’s Writing Style: The AI-BEC Threat Banks Cannot Ignore

    The tell-tale sign of a phishing email used to be the grammar. Awkward phrasing, misaligned tone, a CFO who suddenly writes like a non-native speaker, these were the signals security awareness training taught employees to catch.

    Those signals are gone.

    Generative AI has closed the stylistic gap between a real executive’s writing and a synthetic impersonation. Today, 40% of business email compromise (BEC) phishing emails are AI-generated, producing personalized, contextually accurate messages that match the target executive’s known vocabulary, communication cadence, and organizational context. The click-through rate on AI-crafted lures is 450% higher than on traditional phishing emails. And the financial sector is the primary target.

    For CISOs at banks, insurers, and fintech firms, this is not an incremental escalation of a known threat. It is a qualitative change in what BEC actually is.

    What Is AI-Powered Business Email Compromise?

    Business email compromise (BEC) is a class of fraud where attackers impersonate executives, vendors, or business partners to manipulate employees into transferring funds, divulging credentials, or executing unauthorized transactions. Traditional BEC relied on social engineering and domain spoofing. AI-powered BEC adds stylometric matching, voice cloning, real-time context harvesting from LinkedIn and corporate websites, and automated multi-channel targeting.

    The FBI IC3 reported that BEC caused more than $2.7 billion in adjusted losses in 2024 and accounts for 73% of all reported cyber incidents.

    How the AI-BEC Threat Has Evolved in 2026

    Adversary-in-the-Middle (AiTM) Phishing

    In January 2026, Microsoft documented a multi-stage AiTM phishing and BEC campaign targeting the energy sector via SharePoint. Rather than simply spoofing an email, the attacker positioned themselves between the victim and a legitimate Microsoft authentication flow, intercepting session tokens in real time.

    Dual-Channel BEC Attacks

    The dominant 2026 BEC pattern is the dual-channel attack: simultaneous multi-vector contact where the target receives a spoofed email from an “executive” and a concurrent phone call or SMS confirming the request. The second channel creates urgency and authenticity reinforcement that significantly increases compliance rates.

    Callback Phishing

    Callback phishing, where a phishing email instructs the target to call a fraudulent number staffed by social engineers posing as IT or finance support, more than doubled in popularity in 2025 and continues accelerating into 2026.

    What Happens When Financial Security Teams Don’t Address This

    According to 2026 threat intelligence, 59% of financial services organizations hit by ransomware had their data successfully encrypted. The median ransom demand in financial services reached $3 million.

    The Financial Sector’s Structural Vulnerability

    Attack Vector Why Financial Sector Is Exposed
    Executive impersonation Finance employees are trained to prioritize urgent requests from leadership
    Vendor impersonation High transaction volumes create normalcy for wire transfer requests
    AiTM MFA bypass Widespread MFA adoption has driven attackers to session hijacking rather than credential theft
    AI style matching Executives’ communication styles are well-documented through public statements and filings
    Dual-channel attacks Second communication channel creates false authentication signal

    How Peris.ai Defends Financial Institutions Against AI-BEC

    BrahmaFusion: Behavioral Analytics and Anomalous Communication Detection

    BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform, applies behavioral analytics to communication patterns across email, endpoint, and identity systems. While content filtering can be defeated by stylistically accurate AI-generated text, behavioral analytics focuses on what is unusual about how and when a communication occurs: an executive sending a wire transfer request from an unusual IP, at an unusual hour, to a new payee, without the corresponding approval workflow.

    A FeedLoop customer using BrahmaFusion’s automation reported a 70% reduction in response time for anomalous communication incidents.

    INDRA CTI: Tracking BEC Campaigns Targeting Financial Institutions

    INDRA CTI provides real-time intelligence on threat actor campaigns, including BEC operations targeting specific industries and geographies. When a threat actor group begins targeting the Indonesian banking sector with AiTM infrastructure, INDRA CTI surfaces the relevant indicators before the first targeted email reaches your inbox.

    Use Case: Catching an AI-BEC Attack Before the Wire Transfers

    A regional bank’s CFO receives what appears to be an email from the CEO requesting an urgent $4.2M wire transfer to a new overseas account for a confidential acquisition. The email matches the CEO’s known writing style precisely.

    BrahmaFusion flags the transaction request before it reaches the wire desk:

    • The email originated from an AiTM proxy domain registered 48 hours earlier (INDRA CTI IOC match)
    • The CEO’s actual session shows no corresponding activity in the corporate email system around the email’s timestamp
    • The payee account has no prior relationship in the organization’s transaction history
    • The request bypassed the standard dual-approval workflow required for transfers above $1M

    The BrahmaFusion playbook pauses the request, alerts the SOC and compliance team, and generates a case in Peris.ai IRP with full evidence chain. The attack is neutralized without reaching the wire desk.

    Benefits at a Glance

    Benefit Outcome
    BrahmaFusion behavioral analytics Detects AI-BEC even when content bypasses stylistic filters
    Automated workflow tripwires Wire transfer anomalies caught before human approval stage
    INDRA CTI campaign tracking Known BEC infrastructure blocked before first email lands
    IRP evidence chain Full forensic record for regulatory and legal response
    70% faster response (BrahmaFusion) Rapid containment reduces exposure window for AiTM session hijacks

    The Authentication Stack Is No Longer Sufficient on Its Own

    MFA was the correct response to credential theft. AiTM attacks are the response to MFA. The adversarial cycle does not stop at the authentication layer, and financial institutions that treat identity security as the final defense will be repeatedly outmaneuvered.

    Behavioral analytics, real-time threat intelligence, and automated anomaly response are the layers that catch what authentication cannot. Peris.ai was built to operate at this level, with BrahmaFusion providing the intelligence-driven automation that financial security teams need to stay ahead of AI-powered fraud.

    Visit peris.ai to see how Peris.ai’s agentic AI platform protects financial institutions from the next generation of BEC attacks.

    Frequently Asked Questions

    What is AI-powered BEC?

    AI-powered business email compromise uses generative AI to create hyper-personalized, stylistically accurate executive impersonation emails, increasing click-through rates by up to 450% versus traditional phishing.

    How does adversary-in-the-middle (AiTM) phishing bypass MFA?

    AiTM phishing intercepts a user’s live authentication session, capturing the session token after the user completes genuine MFA. The attacker uses the captured token to authenticate as the user without ever needing the password or MFA code.

    What are the signs of a dual-channel BEC attack?

    An unsolicited request arriving simultaneously via email and phone or SMS, with urgency framing and a request that bypasses normal approval processes, is a strong indicator of a dual-channel BEC operation.

    How much do BEC attacks cost financial organizations?

    The FBI IC3 reported $2.7B+ in BEC-adjusted losses in 2024. The median ransom demand in financial services reached $3 million in 2026.

    How does behavioral analytics catch AI-generated BEC emails?

    Behavioral analytics focuses on communication context, not content: unusual timing, new payees, bypassed workflows, mismatched session activity, and infrastructure anomalies that AI-generated text cannot replicate.

  • Foxconn Was Just the Beginning: How Nitrogen Ransomware Is Putting Manufacturers in Its Crosshairs

    Foxconn Was Just the Beginning: How Nitrogen Ransomware Is Putting Manufacturers in Its Crosshairs

    On May 11, 2026, the Nitrogen ransomware group listed Foxconn on its public leak site, claiming exfiltration of approximately 8TB of data spanning more than 11 million files. Foxconn confirmed disruption to North American operations the following day. Here is why manufacturers are the next major ransomware battleground.

    Foxconn is not a small target. It is one of the largest electronics manufacturers on the planet, a supplier to Apple, Microsoft, and Sony, operating factories on multiple continents. If Nitrogen ransomware can penetrate Foxconn’s North American operations and walk out with 8TB of sensitive data, no manufacturer should consider itself safe.

    This post examines how Nitrogen operates, why the manufacturing sector has become a primary target, and what security architecture prevents an EDR killer from disabling your defences before the encryption begins.

    What Is Nitrogen Ransomware?

    Nitrogen ransomware is a ransomware-as-a-service (RaaS) operation that gained significant attention in 2026 for its targeting of large manufacturing, industrial, and logistics organisations. The group maintains a public leak site, NitroBlog, where it lists confirmed victims and publishes exfiltrated data to pressure ransom payment.

    Nitrogen’s defining technical characteristic is its use of EDR killers as a standard pre-attack preparation step. EDR killers are tools specifically designed to disable, crash, or evade endpoint detection and response software before the ransomware payload is deployed. Their inclusion in Nitrogen’s standard attack playbook reflects a sector-wide trend: Kaspersky’s 2026 International Anti-Ransomware Day report confirmed that EDR killers are now standard components of ransomware attack chains across the industry.

    How Nitrogen Gets In: The Malvertising Initial Access Vector

    Nitrogen does not rely on zero-day exploits for initial access. Its approach is more insidious: malvertising campaigns that deliver trojanized installers of legitimate, trusted software.

    The tools commonly used as lures include:

    • WinSCP (popular Windows file transfer tool)
    • AnyDesk (remote desktop software widely used in manufacturing IT)
    • Advanced IP Scanner (network administration tool)
    • PuTTY (SSH client used by IT and OT teams)

    An IT technician searching for a free download of WinSCP may land on a malvertised page serving a trojanized installer that looks identical to the legitimate version. The installer runs, the legitimate software installs correctly, and in the background Nitrogen’s initial access malware establishes persistence. The technician sees nothing unusual.

    The Foxconn Attack: Timeline and Impact

    • May 11, 2026: Nitrogen lists Foxconn on NitroBlog, claiming exfiltration of 8TB of data across more than 11 million files
    • May 12, 2026: Foxconn publicly confirms disruption to North American operations, affecting facilities in Wisconsin and Texas
    • Scope of data claimed: manufacturing specifications, supplier contracts, employee records, and operational data

    The attack follows a pattern that Nitrogen has repeated across multiple manufacturing sector targets in 2026. The group increasingly favours encryptionless extortion, exfiltrating data and threatening to publish it rather than encrypting systems and demanding a decryption key.

    Why Is Manufacturing a Ransomware Target?

    Operational Technology Exposure

    Modern manufacturing environments blend IT systems with OT (operational technology): industrial control systems, SCADA platforms, programmable logic controllers, and connected assembly-line equipment. These OT systems are often decades old, running software that cannot be updated without re-certifying the manufacturing process.

    High Operational Cost of Downtime

    A ransomware-induced shutdown of a manufacturing line costs thousands to tens of thousands of dollars per hour in lost production.

    Interconnected Supply Chains

    A breach at Foxconn has downstream implications for every organisation in its supply chain.

    What Happens When EDR Is the First Casualty?

    Nitrogen’s EDR killer deployment is specifically designed to neutralise your primary detection capability before the attack proceeds. When EDR is disabled:

    • Endpoint behavioural detection goes dark
    • The ransomware payload deploys without triggering the controls that should stop it
    • Security teams receive no alerts until encryption is already underway
    • Recovery scope expands dramatically because the attack was uncontained

    Nitrogen Attack vs. Defended Environment

    Attack Stage Undefended Environment Peris.ai-Defended Environment
    Malvertised installer download No detection BimaRed surfaces malvertising domain
    EDR killer execution EDR disabled, blind spot created XDR network layer continues detecting
    Lateral movement Undetected across OT/IT boundary NVM packet analysis detects anomalous traversal
    Data exfiltration 8TB exits unnoticed XDR triggers BrahmaFusion isolation playbook
    Ransomware payload Encryption proceeds Automated containment limits blast radius

    How Peris.ai Defends Manufacturing Environments

    Our EDR provides behavioural detection on industrial endpoints and IT workstations. Critically, Peris.ai’s EDR is designed to resist EDR killer techniques through tamper-protection mechanisms.

    Our XDR extends detection to the full manufacturing environment, including OT network segments. In a factory where industrial control systems share network infrastructure with corporate IT, XDR correlates telemetry across both layers.

    Our NVM (Network Visibility Monitor) provides packet-level analysis of all traffic traversing the factory network. Nitrogen’s data exfiltration, typically multi-gigabyte transfers to external infrastructure, generates distinctive network traffic patterns that NVM detects and flags regardless of endpoint agent status.

    BimaRed monitors the attack surfaces that Nitrogen exploits for initial access: internet-facing management interfaces, exposed OT systems, and vulnerabilities in IT administration tools.

    BrahmaFusion ties the detection layers together with automated response playbooks. When XDR or NVM surfaces Nitrogen indicators, BrahmaFusion triggers network segmentation rules that isolate affected systems from OT infrastructure before encryption can spread to production lines.

    Benefits at a Glance

    Benefit Outcome
    EDR with tamper protection EDR killer techniques detected and resisted
    XDR cross-layer visibility OT/IT boundary lateral movement detected
    NVM packet-level analysis Large data exfiltration detected before completion
    BimaRed attack surface monitoring Malvertising domains and exposed assets surfaced early
    BrahmaFusion automated segmentation OT environments isolated before encryption spreads

    Final Thought

    Nitrogen ransomware listed Foxconn on May 11, 2026. The group will list its next target soon. For manufacturing security teams, the question is not whether their sector is being targeted. It is whether their detection architecture will survive an EDR killer long enough to contain the attack.

    Platforms like BrahmaFusion by Peris.ai, combined with XDR, NVM, and INDRA CTI threat intelligence, give manufacturing security teams the layered, agent-independent detection and automated response capability they need to stop Nitrogen and groups like it before the production line goes dark.

    Frequently Asked Questions

    What is Nitrogen ransomware?

    Nitrogen is a ransomware-as-a-service operation that targets manufacturing, industrial, and logistics organisations. The group uses malvertising campaigns to deliver trojanized installers of legitimate tools, deploys EDR killers to disable endpoint detection, and increasingly uses encryptionless extortion by threatening to publish stolen data.

    How did Nitrogen ransomware attack Foxconn?

    On May 11, 2026, Nitrogen listed Foxconn on its leak site claiming 8TB of exfiltrated data across 11 million or more files. Foxconn confirmed disruption to North American operations including facilities in Wisconsin and Texas on May 12, 2026.

    What is an EDR killer and how does it work?

    An EDR killer is a tool designed to disable, crash, or evade endpoint detection and response software before a ransomware payload deploys. By neutralising the primary detection control, attackers create a window where encryption or exfiltration proceeds without triggering alerts.

    Why does Nitrogen use malvertising as an initial access vector?

    Nitrogen uses malvertised downloads of legitimate IT tools (WinSCP, AnyDesk, Advanced IP Scanner, PuTTY) because these tools are trusted and regularly downloaded by IT and OT teams in manufacturing environments.

    How can manufacturers defend against EDR killer attacks?

    Effective defence requires layered detection that operates independently of endpoint agents. This includes network-level visibility (NVM), cross-layer XDR that monitors OT/IT boundaries, EDR with tamper-protection capabilities, and automated isolation playbooks.

  • When the Scalpel Goes Offline: The Stryker Cyberattack and Why Medical Device Security Is Now Critical Care

    When the Scalpel Goes Offline: The Stryker Cyberattack and Why Medical Device Security Is Now Critical Care

    Meta Lede: Stryker was cyberattacked in March 2026. 22% of hospitals have had attacks impact medical devices directly. IoMT security is now a patient safety issue.

    On March 11, 2026, Stryker, one of the world’s largest medical technology companies supplying surgical equipment and devices to hospitals across the globe, was disrupted by a cyberattack affecting operations worldwide.

    This was not a data breach. Stryker’s attack disrupted the operational continuity of a company whose devices are used in operating rooms, ICUs, and emergency departments every hour of every day. And Stryker is not an isolated case. By 2026, 22% of healthcare organizations have experienced cyberattacks that directly impacted medical devices, and 75% of those incidents disrupted patient care. In 24% of medical device attack cases, patients required transfer to other facilities.

    Former FBI officials have proposed terrorist designations for ransomware hackers targeting hospitals, reflecting the recognized severity: when medical devices go offline, patients can die. The Internet of Medical Things (IoMT) is no longer just an IT problem. It is a critical care problem.

    What Is IoMT Security and Why Is It Different from Standard Healthcare IT Security?

    IoMT (Internet of Medical Things) security refers to the protection of network-connected medical devices: infusion pumps, patient monitors, imaging systems, surgical robots, ventilators, diagnostic equipment, and the thousands of other connected devices deployed across modern hospital environments.

    IoMT security differs fundamentally from standard healthcare IT security in three ways:

    • Devices cannot be patched on a normal cycle. Medical device firmware updates require FDA clearance or CE marking in most jurisdictions. A vulnerability disclosed today may not have a patch available for 12 to 18 months.
    • Agents cannot be installed. Most medical devices run proprietary operating systems that cannot accept security agent software. Standard EDR deployment is impossible.
    • Device failure directly harms patients. Unlike an email server outage, a compromised ventilator or infusion pump creates an immediate clinical risk.

    By 2026, smart hospitals deploy more than 7 million IoMT devices globally, double the level from 2021.

    What the Stryker Attack Reveals About Medical Technology Vulnerability

    The March 11, 2026 attack on Stryker demonstrates that the vulnerability extends beyond individual hospital networks to the medical technology supply chain. A cyberattack that disrupts Stryker’s operations can simultaneously affect:

    • Supply chain continuity for hospital procurement teams
    • Software update distribution for connected Stryker devices already deployed in hospitals
    • Remote monitoring and diagnostics capabilities for equipment under service contracts
    • Customer support and technical assistance for clinical staff

    The Scale of the IoMT Security Crisis in 2026

    By the Numbers

    • 7 million+ IoMT devices deployed in smart hospitals globally (double 2021 levels)
    • 22% of healthcare organizations experienced cyberattacks directly impacting medical devices
    • 75% of medical device attacks disrupted patient care
    • 24% of medical device attacks required patient transfers to other facilities
    • $10.9 million average cost of a hospital ransomware attack (downtime, recovery, regulatory fines)
    • 276 million health records breached in 2024 alone

    How Peris.ai Addresses IoMT Cybersecurity

    Agentless Medical Device Monitoring with NVM

    Because agents cannot be installed on medical devices, the detection layer must be network-based. Peris.ai’s NVM (Network Visibility Monitor) performs passive packet-level inspection of medical device network traffic without requiring any software installation on the devices themselves and without causing any device operational impact.

    NVM establishes behavioral baselines for each device type: the normal communication patterns of an infusion pump differ from those of a patient monitor. Deviations from baseline, including unexpected outbound connections, unusual authentication attempts, and command-and-control traffic patterns, trigger alerts without disrupting device function.

    Cross-Network Threat Detection with XDR

    Peris.ai’s XDR platform correlates signals from NVM (medical device network), EDR (clinical IT endpoints), and cloud environments into a unified detection view.

    Automated Clinical Isolation with BrahmaFusion

    BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform, enables automated response playbooks specifically designed to isolate compromised devices without disrupting clinical workflows. When NVM detects anomalous communication from a medical device, a BrahmaFusion playbook can:

    • Isolate the affected device’s network access at the switch level without powering down the device
    • Alert clinical biomedical engineering and the security team simultaneously
    • Trigger a structured incident response workflow via Peris.ai IRP
    • Preserve all network traffic captures for forensic investigation

    Healthcare-Specific Threat Intelligence with INDRA CTI

    INDRA CTI provides healthcare sector-specific threat intelligence: ransomware group tactics targeting medical devices, active campaign IOCs for healthcare-focused threat actors, and vulnerability intelligence for common medical device platforms and operating systems.

    Real-World Scenario: A Ransomware Attack on Hospital IoMT

    A regional hospital system with 2,400 connected medical devices across three facilities:

    • An attacker gains initial access through a phishing email to a hospital IT administrator
    • They move laterally through the hospital IT network to reach the medical device VLAN, which lacks proper segmentation
    • An infusion pump with a known unpatched CVE is exploited as a pivot point into the medical device network
    • Ransomware is deployed targeting the device management server and clinical data systems simultaneously
    • 40 infusion pumps require manual operation; two ICU patients require transfer to another facility
    • Total incident cost: $12.4 million over 8 weeks of recovery

    With Peris.ai: NVM detects the lateral movement into the medical device VLAN. BrahmaFusion isolates the compromised VLAN segment while preserving device function. The infusion pump CVE exploitation is flagged before pivot occurs. INDRA CTI confirms the attacker’s infrastructure matches a known ransomware group’s healthcare campaign.

    Healthcare IoMT Security Priorities

    Priority Action Peris.ai Capability
    1 Deploy agentless network monitoring for all IoMT NVM passive packet inspection
    2 Segment medical device network from general IT NVM-identified boundary enforcement via BrahmaFusion
    3 Inventory all IoMT devices with firmware versions BimaRed asset discovery
    4 Monitor for healthcare-specific threat actor activity INDRA CTI
    5 Test network pivot paths into medical device VLANs Pandava penetration testing

    Conclusion

    The Stryker cyberattack and the data from 2026 make one thing clear: IoMT security is no longer a future concern. With 22% of healthcare organizations already experiencing attacks that directly impact medical devices and 24% of those incidents forcing patient transfers, the question is not whether your hospital will face an IoMT security incident, but whether you will detect it before it reaches patients.

    Peris.ai’s healthcare security stack, built around agentless NVM monitoring, cross-network XDR detection, and clinically aware BrahmaFusion automated response, provides the coverage that standard IT security tools cannot deliver in medical device environments.

    Don’t wait for a breach to take action. Secure your organization today. Stay Secure with Peris.ai.

    Frequently Asked Questions

    What is IoMT cybersecurity?

    IoMT (Internet of Medical Things) cybersecurity refers to the protection of network-connected medical devices including infusion pumps, patient monitors, imaging systems, surgical equipment, and diagnostic devices against cyberattacks that could disrupt clinical operations or compromise patient safety.

    What happened in the Stryker cyberattack in 2026?

    On March 11, 2026, Stryker, one of the world’s largest medical technology companies, was disrupted by a cyberattack affecting its global operations, including supply chain, software update distribution, and technical support capabilities for its connected medical devices.

    Why are medical devices difficult to secure against cyberattacks?

    Medical devices are difficult to secure because they typically run proprietary operating systems that cannot accept security agents, require regulatory approval for firmware updates creating long patch cycles, and cannot be taken offline without clinical risk to patients.

    How common are cyberattacks on medical devices?

    As of 2026, 22% of healthcare organizations have experienced cyberattacks that directly impacted medical devices. Of those, 75% disrupted patient care and 24% required patient transfers to other facilities.

    What is the best way to monitor medical device security without disrupting clinical operations?

    Passive, agentless network monitoring (such as NVM) is the recommended approach. It inspects medical device network traffic at the packet level without installing any software on devices and without causing any operational impact.

  • Your Boss Never Called: How AI Voice Cloning Turned CEO Fraud Into a $2.77 Billion Problem

    Your Boss Never Called: How AI Voice Cloning Turned CEO Fraud Into a $2.77 Billion Problem

    Meta Lede: AI-powered voice cloning made CEO fraud nearly undetectable. BEC losses hit $2.77B. Here’s how the attack is built and what stops it.

    The call lasted four minutes. The voice on the line sounded exactly like the CFO: same cadence, same regional accent, same habit of trailing off before giving a direct instruction. The finance team authorized a $400,000 wire transfer. The CFO never made that call.

    Business email compromise (BEC) has evolved beyond email. Attackers now use generative AI to clone the voices and, increasingly, the video presence of C-suite executives to authorize fraudulent wire transfers, extract credentials, and bypass standard verification procedures. The FBI classifies AI-powered BEC as one of the fastest-growing, highest-value fraud categories targeting enterprises in 2026, with BEC generating $2.77 billion in losses across 21,442 incidents in the most recent FBI IC3 reporting period.

    Detection is nearly impossible in real time. Few tools exist for live audio deepfake detection, and human ears are fundamentally unreliable at identifying AI-generated speech. This post explains exactly how deepfake CEO voice cloning fraud is constructed, why it works, and what controls can actually stop it.

    What Is Deepfake CEO Voice Cloning BEC?

    Deepfake CEO voice cloning BEC is a variant of business email compromise in which attackers use AI-generated audio (and increasingly video) to impersonate senior executives during phone or video calls. Rather than sending a fraudulent email, the attacker places a phone call using a voice synthesized from publicly available audio sources, directing employees to take financial or access-related actions under false authority.

    The FBI reports a 312% spike in AI-assisted cybercrime targeting US citizens between 2024 and 2026. Q1 2026 alone saw 10.7 million BEC attacks, with 4 million occurring in March.

    How AI Voice Cloning Attacks Are Built

    The Preparation Phase

    Attackers invest weeks before placing a single fraudulent call. They harvest voice samples from publicly available sources:

    • Earnings call recordings and investor day presentations
    • Conference keynote videos and panel recordings
    • LinkedIn videos, podcast appearances, and media interviews
    • Company website leadership videos

    Using commercially available AI voice synthesis tools, they train a voice model requiring as little as 30 seconds of clean audio. The result is a synthesized voice that replicates emotional cues: urgency, frustration, reassurance, and fatigue, all of which human listeners rely on to assess credibility.

    The Attack Execution

    Calls are deliberately timed to create pressure: before long weekends, immediately before market close, or during known leadership travel. The attacker calls the finance team, accounts payable department, or IT helpdesk and poses as the CEO, CFO, or other executive.

    In 2026, the dominant tactic is the “dual-channel” attack: a simultaneous voice call, a spoofed email from an executive address, and a spoofed SMS text message all arrive at the same time, creating apparent corroboration across three channels.

    Why Human Detection Fails

    AI-generated voices now replicate micro-level speech patterns including breath timing, hesitation markers, and stress patterns. Independent testing shows that under 3% of hyper-personalized deepfake interactions are detected by their targets using standard listening judgment.

    Why Deepfake CEO Fraud Is Different from Traditional BEC

    Traditional BEC AI Voice Cloning BEC
    Email-only vector Multi-channel: voice, email, SMS simultaneously
    Relies on email spoofing detection Bypasses email security entirely
    Detectable via email header analysis No email artifact to analyze
    Caught by MFA and callback verification Call-back verification spoofed via call forwarding
    Effectiveness declining with awareness Effectiveness increasing with AI quality

    What Controls Actually Stop AI-Powered BEC

    Challenge-Response Safe Words

    The most immediately deployable control is a pre-established verbal safe word protocol between executive leadership and finance/IT teams. Any out-of-band financial or access request must be verified with a shared phrase that was established in person during onboarding and is rotated monthly.

    Mandatory Dual-Approval Delay

    All wire transfers above a defined threshold must require two independent approvals with a mandatory cooling-off period. No single voice call or message, regardless of claimed authority, can authorize a transfer without a second approver confirming through a separate verification path.

    AI-Powered Anomaly Detection with BrahmaFusion

    BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform, can monitor for unusual financial authorization patterns: requests arriving outside business hours, transfers to first-time beneficiary accounts, requests placed before public holidays, and dual-channel simultaneous contact patterns.

    Incident Response Workflow with Peris.ai IRP

    When a suspected CEO fraud attempt is detected or reported, a structured incident response workflow is essential. Peris.ai IRP provides unified case management to coordinate rapid investigation. Organizations using Peris.ai IRP have achieved 35% analyst workload reduction through this structured approach.

    Threat Actor Attribution with INDRA CTI

    INDRA CTI, Peris.ai’s cyber threat intelligence platform, tracks deepfake BEC campaign infrastructure: spoofed caller ID pools, campaign timing patterns, and affiliate groups operating specific CEO fraud campaigns.

    Security Testing with Pandava

    Pandava, Peris.ai’s penetration testing platform, includes social engineering scenarios specifically designed around simulated deepfake calls.

    Real-World Scenario: A Dual-Channel CEO Fraud Attack

    A regional bank’s CFO is traveling internationally for a conference:

    • Attackers monitor the CFO’s LinkedIn and conference social media to confirm travel dates
    • On Friday afternoon, three simultaneous contacts arrive: a spoofed email from the CFO’s address, a spoofed SMS from the CFO’s number, and a voice call using an AI-cloned version of the CFO’s voice
    • The voice call requests an urgent $650,000 wire transfer to a new vendor account, citing a confidential acquisition
    • The finance coordinator, seeing email and SMS corroboration, initiates the transfer
    • Total time from first contact to wire authorization: 11 minutes

    With BrahmaFusion’s anomaly detection: the new beneficiary account, Friday afternoon timing, and simultaneous multi-channel contact pattern trigger an automated hold and escalation. The transfer is flagged for manual review before execution. The fraud is stopped.

    Benefits of an AI-Aware BEC Defense Program

    Benefit Outcome
    Behavioral anomaly detection Catch unusual authorization patterns before transfer executes
    Structured IR workflow Coordinate response across finance, legal, and security in one platform
    Threat actor tracking Pre-flag known BEC campaign infrastructure
    Simulated deepfake testing Build staff resilience before real attacks arrive
    Dual-approval enforcement Remove single-point-of-failure in authorization chains

    Conclusion

    AI voice cloning has turned CEO fraud from an email problem into a multi-channel social engineering crisis. With $2.77 billion in losses and a 312% increase in AI-assisted cybercrime, organizations that rely solely on email security controls are defending against the wrong threat vector.

    The controls that work are behavioral, not perceptual: anomaly detection that flags unusual authorization patterns, structured incident response that creates mandatory friction, and security testing that trains your teams before attackers do. Peris.ai’s integrated platform gives security and finance teams the tools to detect, respond to, and learn from deepfake BEC attempts before they become wire transfer losses.

    Don’t wait for a breach to take action. Secure your organization today. Stay Secure with Peris.ai.

    Frequently Asked Questions

    What is deepfake CEO voice cloning fraud?

    Deepfake CEO voice cloning fraud is a form of business email compromise (BEC) in which attackers use AI-synthesized audio to impersonate C-suite executives during phone calls, directing employees to authorize wire transfers, share credentials, or bypass standard verification procedures.

    How do attackers create a deepfake voice for CEO fraud?

    Attackers collect voice samples from public sources such as earnings calls, conference videos, and podcast recordings. Using AI voice synthesis tools, they train a voice model requiring as little as 30 seconds of audio, producing a synthetic voice that replicates the target’s speech patterns and emotional cues.

    How much money has been lost to BEC and deepfake CEO fraud?

    The FBI reports $2.77 billion in BEC losses across 21,442 incidents in the most recent IC3 reporting period. AI-assisted cybercrime targeting US citizens increased 312% between 2024 and 2026.

    Can deepfake phone calls be detected in real time?

    Industry testing shows that fewer than 3% of hyper-personalized deepfake interactions are detected by their targets in real time. Human listeners cannot reliably distinguish AI-generated speech, particularly under time pressure.

    What is the most effective control against AI voice cloning BEC?

    A combination of pre-established verbal safe words, mandatory dual-approval delays for financial transfers, AI-powered behavioral anomaly detection (such as BrahmaFusion), and regular simulated deepfake testing (such as Pandava) provides the most effective layered defense.

  • QR Codes Are the Phishing Vector Your Security Team Is Not Watching: They Doubled in Q1 2026

    Meta Lede: QR code phishing doubled in Q1 2026, making it the fastest-growing attack vector. Here’s why quishing bypasses email security and what stops it.

    Your email security gateway caught 8.3 billion phishing threats in Q1 2026. It almost certainly missed the fastest-growing one.

    QR code phishing, known as “quishing,” more than doubled in Q1 2026, according to Microsoft’s Q1 2026 Email Threat Landscape Report released April 30, 2026. It is now the fastest-growing attack vector in email-based threat data. The reason it bypasses your existing defenses is by design: QR codes contain no URL, only an image. Legacy email scanners that analyze link reputation and URL patterns have nothing to analyze. The malicious destination is invisible to automated scanning tools until the victim’s phone decodes it.

    And that phone, in virtually every enterprise environment, has far weaker security controls than the corporate laptop sitting next to it.

    This post explains exactly how QR code phishing 2026 works, why it is so difficult to detect with standard tools, and what security teams can add to close the gap.

    What Is QR Code Phishing (Quishing)?

    Quishing is a phishing attack that uses QR codes instead of embedded hyperlinks as the delivery mechanism. Rather than including a malicious URL that email security gateways can inspect and block, the attacker embeds a QR code image in the email or physical medium. The code itself contains the malicious URL, but this URL is not readable by text-based email scanning tools.

    The victim scans the QR code with their mobile device, which resolves the URL and delivers the phishing payload or credential harvesting page. Because mobile devices typically operate on personal or unmanaged networks (home Wi-Fi, cellular data) and lack enterprise-grade endpoint protection, the payload executes in an environment with significantly weaker security controls than the corporate perimeter.

    Between Q1 2026, a multi-stage campaign targeted 35,000 users across 26 countries using QR-linked payloads as the primary delivery mechanism.

    Why QR Code Phishing Doubles in Q1 2026

    The Email Security Bypass Architecture

    The core reason quishing is growing is that it was engineered specifically to defeat email security gateways. Standard email security controls that fail against quishing include:

    • URL reputation scanning: No URL is present in the email body; the QR code is an image
    • Link rewriting and sandboxing: Cannot rewrite what does not appear as a link
    • Content analysis: The malicious destination is encoded in the image, not accessible to text analysis
    • Attachment scanning: A QR code image does not match malware signatures

    The email that delivers a QR phishing payload can pass every standard email security check with a perfect score.

    CAPTCHA-Gated Payloads: A Secondary Evasion Layer

    Microsoft’s Q1 2026 data documents a parallel evolution: CAPTCHA-gated phishing, which grew rapidly alongside quishing in Q1. After the victim scans the QR code and loads the phishing page, the page requires a CAPTCHA completion before displaying the credential harvesting form. This prevents automated security analysis tools from reaching the payload page, making sandbox-based detection ineffective.

    The Mobile Device Security Gap

    The QR scanning device is typically a personal smartphone. In most enterprise environments:

    • Personal smartphones are not enrolled in Mobile Device Management (MDM)
    • They operate on personal networks outside enterprise security monitoring
    • They lack the endpoint protection installed on corporate laptops
    • Browser-level phishing protections on mobile are less mature than on desktop

    Physical Environment Expansion

    Quishing is no longer confined to email. In 2026, QR codes are being deployed as attack vectors in physical environments:

    • Fake QR codes pasted over legitimate ones at parking payment stations
    • Malicious QR codes embedded in conference badge lanyards and event materials
    • Phishing QR codes placed on posters in office reception areas and public spaces
    • Fake package delivery notifications with QR codes sent via physical mail

    The 2026 Quishing Threat Landscape: By the Numbers

    Metric 2026 Data Point
    QR phishing growth, Q1 2026 More than doubled quarter-over-quarter
    Total email phishing threats, Q1 2026 8.3 billion detected by Microsoft
    BEC attacks total, Q1 2026 10.7 million (January surge 24%, March surge 26%)
    Multi-country campaign scale 35,000 users targeted across 26 countries with QR payloads
    Hyper-personalized AI phishing detection rate Under 3% by standard security tools

    How Peris.ai Defends Against Quishing Attacks

    AI-Powered Phishing Response with BrahmaFusion

    BrahmaFusion, Peris.ai’s agentic AI and hyperautomation platform, automates the response to phishing alerts including quishing incidents. When a user reports a QR phishing email or an anomalous mobile login is detected following QR code scanning, BrahmaFusion triggers a response playbook: the suspicious email is quarantined across all recipients, the session credentials are flagged for forced re-authentication, the QR code image is extracted and submitted for reputation analysis, and the SOC is notified with a fully enriched alert package.

    Mobile and Endpoint Detection with XDR

    Peris.ai’s XDR platform extends detection to cover mobile and endpoint behavior following QR code interactions. When a device accesses a newly registered domain immediately after a QR code was reported in the environment, or when credential entry is followed immediately by an anomalous login from an unusual location, XDR correlates these signals into a high-confidence alert.

    Campaign Tracking with INDRA CTI

    INDRA CTI, Peris.ai’s threat intelligence platform, tracks active quishing campaigns in real time: QR code infrastructure domains, campaign-specific payload patterns, and threat actor attribution for organized quishing operations.

    Simulated Quishing Testing with Pandava

    Pandava, Peris.ai’s penetration testing platform, includes simulated quishing attacks as part of social engineering assessment programs.

    Real-World Scenario: A Quishing Attack Against a Finance Team

    A finance director at a regional bank receives an email appearing to come from the bank’s IT department:

    • The email explains that multi-factor authentication is being upgraded and provides a QR code to complete enrollment
    • The email passes all email security gateway checks (no URL, no malware signature, trusted sender display name)
    • The finance director scans the QR code during a commute using their personal smartphone
    • The QR code resolves to a CAPTCHA-gated credential harvesting page mimicking the bank’s MFA portal
    • The finance director completes the CAPTCHA and enters their username, password, and MFA code
    • Attackers use the harvested credentials within 4 minutes to initiate a session on the corporate banking platform
    • $380,000 is transferred to an external account before the session triggers a behavioral alert

    With Peris.ai: BrahmaFusion detects the anomalous login and forces re-authentication. INDRA CTI flags the destination domain as a known quishing campaign infrastructure. The transfer is blocked pending manual approval.

    Quishing Defense Checklist

    Control Why It Helps
    QR-aware email security Detect and sandbox QR code images before delivery
    Mobile Device Management Extend endpoint security to devices used for QR scanning
    Behavioral login anomaly detection Catch credential misuse following successful quishing
    Real-time campaign threat intel Block known quishing domains before victims access them
    Simulated quishing training Build staff recognition before real attackers test them

    Conclusion

    QR code phishing doubled in Q1 2026 for the same reason any attack vector grows: it works. It bypasses email security gateways by design, exploits the security gap of unmanaged mobile devices, and is now expanding beyond email into physical environments.

    Peris.ai’s combination of BrahmaFusion automated response, XDR behavioral detection, and INDRA CTI campaign intelligence gives security teams the multi-layer coverage needed to catch quishing attacks at the delivery, credential theft, and post-compromise stages.

    Don’t wait for a breach to take action. Secure your organization today. Stay Secure with Peris.ai.

    Frequently Asked Questions

    What is QR code phishing (quishing)?

    Quishing is a phishing attack that uses QR codes instead of embedded URLs to deliver malicious payloads. The QR code contains the malicious destination but appears as an image to email scanning tools, bypassing URL-based security checks.

    How much did QR code phishing grow in 2026?

    According to Microsoft’s Q1 2026 Email Threat Landscape Report, QR code phishing more than doubled in Q1 2026, making it the fastest-growing attack vector in email-based threat data for the quarter.

    Why does quishing bypass email security gateways?

    Email security gateways analyze text-based content, URLs, and file attachments. QR codes are images that contain no readable URL, so gateway tools have nothing to inspect or block.

    What is CAPTCHA-gated phishing?

    CAPTCHA-gated phishing places a CAPTCHA verification step between the victim and the credential harvesting page. This prevents automated security analysis tools from reaching the malicious payload, making sandbox-based detection ineffective.

    How can organizations protect against quishing attacks?

    Effective defenses include QR-aware email security, mobile device management, behavioral login anomaly detection, real-time threat intelligence to block known quishing domains, and simulated quishing exercises to train employees.

  • LLMjacking and Criminal AI: How Attackers Are Turning Your AI Infrastructure Into Their Weapon

    LLMjacking and Criminal AI: How Attackers Are Turning Your AI Infrastructure Into Their Weapon

    More than 90,000 LLMjacking attempts were logged between late 2025 and early 2026. Criminal AI toolkits have removed safety guardrails from large language models and made sophisticated attacks accessible at industrial scale. Your AI infrastructure is now an attack surface.

    The AI revolution in enterprise technology has a shadow side that most organisations are not yet defending against. While security teams focus on AI-powered phishing and deepfake fraud, a different category of threat has matured quietly: attacks against AI infrastructure itself.

    LLMjacking is the act of hijacking an organisation’s AI infrastructure to run compute-intensive tasks at the victim’s expense. It is analogous to cryptojacking but targets GPU-backed inference endpoints instead of CPU cycles. Meanwhile, a parallel criminal AI ecosystem has emerged, purpose-built to remove the safety controls of mainstream AI models and make sophisticated cyberattacks, fraud, and social engineering accessible to anyone willing to pay a subscription fee.

    This post examines both threats, the data behind their scale, and what security teams need to do before their AI investment becomes someone else’s attack platform.

    What Is LLMjacking?

    LLMjacking is the unauthorised use of an organisation’s AI model infrastructure, typically cloud-hosted LLM endpoints, to run inference tasks for the attacker’s benefit. The attacker does not steal data in the traditional sense. Instead, they consume the organisation’s compute resources, generating costs that can reach tens of thousands of dollars per day at scale.

    The attack vector is straightforward: misconfigured API keys, exposed inference endpoints, and vulnerable proxy configurations give attackers access to AI services. Automated scanners probe for these exposures continuously. More than 90,000 LLMjacking attempts were logged between late 2025 and early 2026, driven largely by misconfigured open proxies that provide access to LLM service APIs.

    The Criminal AI Toolkit Ecosystem

    Parallel to LLMjacking, a mature criminal AI ecosystem has developed specifically to remove the ethical and safety guardrails that mainstream AI providers have built into their models. These purpose-built criminal LLMs serve the same function as legitimate AI models, but without restrictions on harmful content:

    • WormGPT: generates convincing phishing emails, social engineering scripts, and malware code without the refusals that ChatGPT or Claude would produce
    • WolfGPT: focused on financial fraud and business email compromise script generation
    • EscapeGPT: specialises in jailbreaking and circumventing AI safety mechanisms
    • FraudGPT: used for generating fake invoices, fraudulent financial documents, and identity theft scripts
    • GhostGPT: targeted at creating evasive malware and exploit code

    These tools are not hypothetical. They are available on underground markets with subscription pricing ranging from $100 to $1,500 per month, making sophisticated attack capabilities accessible to threat actors with minimal technical background.

    The CrowdStrike 2026 Global Threat Report documented an 89% increase in AI-enabled adversary activity in 2025 compared to the prior year. All four major nation-state actors, China, Russia, Iran, and North Korea, had operationalised large language models in their attack chains by late 2025.

    CVE-2025-53773: When AI Development Tools Become Attack Surfaces

    The security risk of AI infrastructure extends beyond criminal toolkits. CVE-2025-53773 is a prompt injection vulnerability in GitHub Copilot that carries a CVSS score of 9.6. By embedding malicious instructions in pull request descriptions, an attacker could cause GitHub Copilot to execute arbitrary code on a developer’s workstation.

    This vulnerability illustrates a category of risk that security teams are not yet systematically addressing: the AI tools embedded in the development workflow are themselves attack surfaces. Every AI-assisted code review, every AI-generated pull request summary, and every AI-powered development tool introduces a new vector for prompt injection, model manipulation, and supply chain compromise.

    What Happens When AI Security Is Overlooked?

    Organisations that deploy AI infrastructure without corresponding security controls face multiple compounding risks:

    • Financial: LLMjacking can generate unexpected cloud bills of $10,000 to $50,000 or more per day when attackers run compute-intensive inference tasks at scale
    • Operational: Consumed API quotas disable legitimate AI-powered workflows
    • Data exposure: Attackers with access to AI inference endpoints may be able to extract training data or previous conversation context through prompt injection
    • Competitive: Proprietary models trained on internal data may be accessible to attackers via compromised API endpoints
    • Reputational: AI infrastructure used to generate attacker content may create attribution and liability issues

    AI Security: Traditional Posture vs. AI-Aware Defence

    Risk Category Without AI Security With Peris.ai AI Security
    LLMjacking detection Discovered via unexpected invoice BrahmaFusion detects anomalous AI API usage patterns
    Criminal AI toolkit awareness Unknown until breach INDRA CTI tracks criminal AI infrastructure and TTPs
    AI development tool vulnerabilities Unmonitored in CI/CD pipeline BimaRed SAST scans AI/ML pipeline code for injection vulnerabilities
    Prompt injection in production No detection capability XDR monitors AI service interactions for anomalous patterns
    Post-compromise response Manual investigation Peris.ai IRP case management with AI-specific playbooks

    How Peris.ai Secures AI Infrastructure

    INDRA CTI tracks the criminal AI toolkit ecosystem continuously. WormGPT, FraudGPT, GhostGPT, and their successors are monitored through their infrastructure, distribution channels, and capability updates. When a new criminal AI toolkit is identified that targets a specific sector or is observed being used in campaigns against organisations similar to yours, INDRA CTI delivers that intelligence to your security team as actionable context rather than a news item.

    BimaRed applies SAST to your AI and ML pipeline code. Prompt injection vulnerabilities, like CVE-2025-53773, are a class of code-level issue that static analysis can identify. BimaRed scans AI pipeline code for unsafe prompt handling patterns, unsanitised user input passed to model APIs, and dependencies with known AI-related vulnerabilities.

    BrahmaFusion detects anomalous AI API usage through behavioural monitoring. LLMjacking generates distinctive patterns: sudden spikes in API calls, unusual times of day for high-volume inference requests, calls from unexpected IP addresses or service identities, and consumption patterns inconsistent with legitimate business workflows. BrahmaFusion triggers automated isolation playbooks when these patterns are detected, revoking the compromised credentials and blocking the offending access before the bill arrives.

    Our XDR provides cross-layer detection for AI cloud service abuse. In cloud environments where AI inference runs alongside other workloads, XDR correlates anomalous AI service activity with related indicators in identity logs, network traffic, and endpoint activity to build a complete picture of the attack chain.

    Scenario: Catching LLMjacking Before the $40,000 Bill

    At 2:30am, BrahmaFusion detects an anomaly in the organisation’s AI inference endpoint usage: API call volume has increased 8,000% over baseline in the past 45 minutes. The calls are originating from an IP not associated with any known service identity.

    With Peris.ai:

    • BrahmaFusion immediately flags the anomalous API consumption pattern
    • INDRA CTI matches the source IP to known LLMjacking infrastructure from a scanning campaign identified the prior week
    • The compromised API key is revoked automatically
    • The inference endpoint is temporarily restricted to approved IP ranges pending investigation
    • Peris.ai IRP opens a case documenting the incident for the cloud security team
    • Estimated cost of the LLMjacking attempt if undetected for 24 hours: $38,000. Cost of the containment: 12 minutes of automated response.

    Benefits at a Glance

    Benefit Outcome
    INDRA CTI criminal AI monitoring WormGPT, FraudGPT, and LLMjacking infrastructure tracked in real time
    BimaRed AI pipeline SAST Prompt injection vulnerabilities caught before deployment
    BrahmaFusion API anomaly detection LLMjacking detected and contained before significant cost accumulates
    XDR cloud AI service monitoring Full cross-layer visibility into AI infrastructure abuse

    Final Thought

    The AI infrastructure your organisation has invested in, the inference endpoints, the model APIs, the development tools with AI integration, is now part of your attack surface. The criminal ecosystem that has grown up around AI in 2025 and 2026 treats it as a resource to be exploited and a capability to be weaponised.

    Platforms like BrahmaFusion by Peris.ai, combined with INDRA CTI’s criminal AI tracking and BimaRed’s AI pipeline security, give security teams the visibility and automated response needed to protect AI investments from becoming attacker infrastructure.

    Frequently Asked Questions

    What is LLMjacking?

    LLMjacking is the unauthorised use of an organisation’s AI model infrastructure to run inference tasks at the victim’s expense. Attackers exploit misconfigured API keys or exposed inference endpoints to consume AI compute resources, generating costs of up to $50,000 or more per day. More than 90,000 LLMjacking attempts were logged between late 2025 and early 2026.

    What are criminal AI tools like WormGPT and FraudGPT?

    Criminal AI toolkits are purpose-built large language models that remove the safety guardrails of mainstream AI models. WormGPT generates phishing emails and malware code. FraudGPT creates fraudulent financial documents. GhostGPT produces evasive malware. These tools are available on underground markets for $100 to $1,500 per month.

    What is CVE-2025-53773 in GitHub Copilot?

    CVE-2025-53773 is a prompt injection vulnerability in GitHub Copilot with a CVSS score of 9.6. By embedding malicious instructions in pull request descriptions, an attacker could cause GitHub Copilot to execute arbitrary code on a developer’s machine.

    How can organisations detect LLMjacking attempts?

    Effective LLMjacking detection requires monitoring AI API usage for anomalous patterns: sudden spikes in call volume, requests from unexpected IP addresses or service identities, and consumption patterns inconsistent with normal business workflows. BrahmaFusion’s behavioural monitoring detects these patterns and triggers automated credential revocation before significant cost accumulates.

    How has nation-state use of AI in attacks evolved?

    According to CrowdStrike’s 2026 Global Threat Report, all four major nation-state actors (China, Russia, Iran, North Korea) had operationalised LLMs in their attack chains by late 2025, and AI-enabled adversary activity increased by 89% in 2025 versus the prior year.