Blog

  • Spirals Ransomware Recovery Services

    Spirals Ransomware Recovery Services


    Spirals ransomware can move from a compromised server to widespread encryption in less than a day. Learn how this Rust-based threat operates, which warning signs matter, and how to contain an incident before restoring affected systems.

    Rapid containment matters when a ransomware intrusion moves across the network in hours.

    In the first publicly documented Spirals incident, attackers combined credential theft, remote administration tools, security-service disruption, and data-extortion pressure before and during encryption.

    What Is Spirals Ransomware?

    Spirals is a Rust-based file-encrypting ransomware family documented in a June 2026 intrusion at an IT services company in South Asia. The case combined encryption with a threat to disclose stolen information, creating both operational and data-exposure concerns. The operator has not been conclusively linked to an established ransomware group, and the publicly documented case should not be mistaken for a complete profile of every future Spirals attack.

    The malware used a separate AES-128 key for each file, protected those keys with an attacker-controlled ECDH P-256 public key, and encrypted parts of larger files to accelerate the process. Those implementation details matter to investigators, but the first priority for an affected organization is stopping active access and establishing a trustworthy recovery path.

    Why This Campaign Matters

    According to the Symantec Threat Hunter Team, the known intrusion progressed from an exposed web server to ransomware deployment across the victim network in less than 24 hours. That short window leaves little time to respond if suspicious web-server activity, stolen credentials, or remote execution is treated as an isolated event.

    The attack also targeted services that support backups, databases, and virtual machines. Interrupting those services can broaden the outage and complicate restoration. A ransom note’s promise to publish data means successful backup recovery alone may not resolve the incident; teams also need to determine what information was accessed or removed.

    How the Intrusion Chain Works

    In the documented case, attackers entered through an internet-facing Microsoft IIS server and installed an ASP.NET web shell. They then established additional remote-access channels, created a local account, enabled RDP, and gathered credentials from Windows systems. WMI activity carried the intrusion to other hosts, while PsExec was later used to distribute the ransomware payload with elevated privileges.

    Before encryption, the operators attempted to weaken endpoint defenses and stop a wide range of backup, database, and virtualization services. The payload was staged under a name resembling a legitimate Windows utility. These observations describe one investigated incident; they do not establish that every Spirals intrusion will use the same entry point or tools. See the Symantec Threat Hunter Team’s technical analysis for the underlying research.

    Common Signs of a Spirals-Linked Intrusion

    • Unexpected web-shell or command execution activity on an internet-facing IIS server
    • New local accounts, unusual RDP enablement, or unexplained remote-access tunnels
    • Credential-dumping activity or rapid WMI connections across multiple hosts
    • PsExec or PowerShell commands pushed broadly from a single system
    • Endpoint protection changes or backup, database, and virtualization services stopping unexpectedly
    • Unfamiliar encryption activity, a Spirals-related ransom note, or credible data-theft indicators

    Our Spirals Ransomware Recovery Services

    Immediate Incident Response and Containment

    The response begins by isolating affected systems and restricting the access paths the attacker may still control. Preserving logs, memory, and other evidence before widespread rebuilding helps investigators establish the sequence of events and supports later exposure assessment.

    Threat Hunting, Eradication, and Attacker Ejection

    Investigators should trace the initial web-server compromise, review privileged account use, identify remote-access tools and persistence, and determine which systems were reached through WMI or PsExec. Access should be removed comprehensively, with affected credentials rotated in a controlled sequence.

    Recovery and Restoration

    Recovery planning should validate backup integrity, prioritize essential workloads, and confirm that restored systems are not reconnected to an active intrusion. Backup, database, and virtualization dependencies need particular attention when service disruption preceded encryption.

    Post-Incident Hardening

    After operations stabilize, organizations can address the exposed entry point, strengthen privileged access and segmentation, review remote administration controls, and improve detection for lateral movement and security-service tampering.

    Why Organizations Need to Take Spirals Seriously

    The known attack demonstrates how quickly a web-server foothold can become an enterprise-wide incident when privileged credentials and remote administration tools are available. Intermittent encryption of larger files can shorten the time between payload deployment and business disruption, while a data-theft claim adds a separate investigation and notification challenge.

    Spirals remains a relatively new family, so organizations should avoid assuming its full victim profile or future methods are already known. A response should be guided by evidence from the affected environment, not by a fixed checklist of indicators from one case.

    Why Work With Alvaka

    Alvaka helps organizations coordinate containment, forensic investigation, attacker removal, backup validation, and restoration when ransomware disrupts business-critical systems. The aim is to recover safely while understanding the intrusion and reducing the chance of a repeat compromise.

    Contact Alvaka for Spirals Ransomware Recovery Services

    If your organization is investigating suspected Spirals activity or recovering from a ransomware incident, contact Alvaka for help containing the threat and planning a safe return to operations.

    Our ransomware response and recovery team is available 24/7, 365 days a year.

  • ImNotAVillain Data Extortion

    ImNotAVillain Data Extortion


    ImNotAVillain is an emerging data-extortion threat, not a confirmed file-encrypting ransomware family. Organizations should assess public claims, protect sensitive information, and investigate possible unauthorized access without assuming encryption occurred.

    A public data-theft claim calls for fast, evidence-led investigation. The priority is to determine whether access occurred, what information may be exposed, and whether the actor retains a way back in. An extortion statement is a lead to investigate, not proof of a complete breach narrative.

    What Is ImNotAVillain?

    ImNotAVillain is an emerging cyber-extortion threat first tracked publicly in September 2026. WatchGuard categorizes it as a data-broker actor. That classification reflects its apparent emphasis on information and public pressure; it does not establish a distinct encryptor or a repeatable ransomware deployment method.

    Public victim listings and actor statements are useful leads, but they are not independent confirmation that every named organization was breached or that every advertised data set is authentic. SOCRadar labels the currently tracked listings as claims. Technical reporting on the operator, initial access, malware, and broader methodology remains limited.

    Why This Campaign Matters

    Data extortion can create serious business consequences without locking a single endpoint. If sensitive records were obtained, an organization may need to evaluate customer and employee exposure, contractual obligations, regulatory requirements, and the risk of follow-on fraud while normal operations continue.ImNotAVillain has drawn attention through claims involving Revolut and alleged Italian government or law-enforcement information. Revolut confirmed that fraudulent requests sent from a legitimate government-agency email domain led to an unauthorized disclosure of some customer data. That disclosure does not, by itself, verify the actor’s full account of its role or its separate claims about Italian records.

    How the Intrusion Chain Works

    There is no well-documented ImNotAVillain intrusion chain that organizations can safely treat as a standard playbook. A suspected incident should be reconstructed from evidence: account sign-ins, remote access, cloud and application audit trails, data exports, third-party requests, administrative changes, and outbound transfer records.Investigators should also examine whether sensitive information was disclosed through a business process rather than malware on an endpoint. The reported Revolut event illustrates why verifying the identity and authority behind a request matters even when a message appears to come from a legitimate domain. No specific entry method should be attributed to ImNotAVillain in another environment without supporting evidence.

    Common Signs That Require Investigation

    • An extortion message or public listing that names the organization or presents a plausible data sample
    • Unexplained access to sensitive repositories, customer records, or shared cloud storage
    • Unusual data exports, large downloads, or transfers from privileged accounts
    • Information requests or disclosures that bypass established identity-verification steps
    • New accounts, changed permissions, or remote sessions without a business explanation
    • Evidence that allegedly exposed records are genuine, current, and tied to the organization

    None of these indicators alone proves ImNotAVillain involvement. They are starting points for scoping unauthorized access and testing an actor’s claims.

    Our ImNotAVillain Data Extortion Response Services

    Immediate Incident Response and Containment

    The first steps are to preserve evidence, restrict accounts or integrations that may be abused, protect sensitive repositories, and establish a coordinated response. Containment should be proportionate to confirmed activity so investigators do not destroy the records needed to understand the event.

    Threat Hunting, Eradication, and Attacker Ejection

    Review identity, endpoint, cloud, and application records to determine whether unauthorized access remains active. Remove confirmed persistence, rotate affected credentials in a controlled sequence, and verify that the access path has been closed.

    Recovery and Restoration

    In a data-extortion case, recovery may center on restoring control of accounts and workflows rather than decrypting systems. Teams should establish what information was accessed or disclosed, validate the integrity of critical systems, and coordinate notification decisions with appropriate legal and business stakeholders.

    Post-Incident Hardening

    Strengthen privileged access, logging, data-export controls, third-party request verification, and incident response procedures. The objective is to reduce both unauthorized access and improper disclosure through trusted-looking communications.

    Why Organizations Need to Take ImNotAVillain Seriously

    An unverified extortion claim should not be accepted at face value, but it should not be ignored. Attackers can exploit uncertainty by publishing selective samples, setting deadlines, or contacting affected parties directly. Evidence preservation and careful validation give leaders a factual basis for decisions under pressure.Because no ImNotAVillain encryptor or affiliate structure has been reliably established in public reporting, organizations should avoid assuming this is a conventional ransomware-recovery problem. The central questions are whether information was accessed, how it was obtained, who may be affected, and whether the actor still has access.

    Why Work With Alvaka

    Alvaka helps organizations investigate cyber-extortion claims, contain unauthorized access, assess potential data exposure, and coordinate technical recovery. A disciplined response separates verified findings from attacker assertions while protecting the systems and records needed for business continuity.

    Contact Alvaka for ImNotAVillain Data Extortion Response

    If your organization has received an ImNotAVillain claim or discovered signs of unauthorized data access, contact Alvaka for help preserving evidence, investigating the scope, and planning the next steps.

  • 0x00 Ransomware Recovery Services

    0x00 Ransomware Recovery Services


    What Is 0x00?

    0x00 is an emerging threat name associated with alleged victim disclosures in ransomware and cyber extortion tracking. SOCRadar’s group profile records its first observed activity in October 2026 and identifies no reported tactics or initial-access methods.

    That distinction matters when responding to a claim. A listing on a ransomware tracking platform does not, by itself, confirm that files were encrypted, what information was accessed, or whether an attacker remains inside the environment. Those questions require technical investigation.

    0x00 Victims and Targeted Industries

    Public tracking includes a claim naming bienestarempresarial, an organization classified in Mexico’s professional services sector. The record was discovered on October 15, 2026 and is labeled claimed, not independently confirmed.

    This early listing is not enough to establish a consistent targeting pattern or conclude that 0x00 operates only in Mexico. For professional services businesses, the immediate concern is whether client information, shared workspaces, or accounts used to deliver services were exposed.

    How 0x00-Related Incidents Are Investigated

    An investigation should test the allegation against the organization’s own records rather than begin with an assumed 0x00 attack sequence. Important areas include:

    • Identity and remote access: Review unfamiliar sign-ins, external sessions, privilege changes, and use of shared or administrative accounts.
    • Endpoint and server activity: Examine suspicious processes, unauthorized software, account creation, and persistence on systems implicated by the claim.
    • Data access and movement: Check sensitive repositories, unusual archives, large downloads, and outbound transfers to assess possible exposure.
    • Operational and recovery resources: Determine whether applications, identity services, backups, or storage have been changed or disrupted.

    Preserve evidence while coordinating containment. The CISA #StopRansomware Guide provides general response guidance; these investigation areas are not verified 0x00-specific techniques.

    Potential Business Impact of a 0x00 Incident

    The consequences depend on what the investigation confirms. An extortion demand can require a response even when applications remain available.

    Client and Business Information Exposure

    Access to client files, personnel information, contracts, or confidential business records may create exposure questions. Determine what was accessible and whether evidence supports the removal of information before deciding how to describe the incident.

    Disruption to Service Delivery

    Compromised accounts or unavailable systems can interrupt shared work, customer communications, and time-sensitive services. Recovery priorities should reflect the applications and dependencies needed to resume those activities safely.

    Unauthorized Access That Remains Active

    Normal-looking operations do not establish that suspicious access has ended. If compromised credentials or unauthorized remote connections remain usable, an organization may face further access or disruption after the first demand.

    Recovery and Exposure Assessment

    Trusted backups can help restore damaged systems, but cannot reverse a data disclosure. Confirmed system disruption and possible information exposure need coordinated workstreams rather than treating restoration as the end of the incident.

    Alvaka’s 0x00 Ransomware Response and Recovery Services

    Alvaka helps organizations investigate suspected compromises, contain confirmed threats, and plan the recovery of affected IT systems. Support can include identity and endpoint review, exposure assessment, attacker removal, backup evaluation, and restoration planning.

    Our team works with internal IT personnel to connect the investigation with operational recovery. Where public intelligence is limited, decisions should be driven by evidence from the affected environment rather than assumptions about a threat actor’s capabilities.

    Frequently Asked Questions About 0x00

    What is 0x00 ransomware?

    0x00 is a threat name appearing in ransomware and cyber extortion tracking. Public information describes alleged victim disclosures, but does not yet establish a detailed technical profile of the operation.

    Who has 0x00 claimed to target?

    Public tracking includes a claim involving bienestarempresarial, classified as a professional services organization in Mexico. A leak-site listing is not independent confirmation of a breach and does not establish the full scope of any incident.

    Is file encryption confirmed in 0x00 incidents?

    The public reporting reviewed for this page does not establish a verified 0x00 encryption method or demonstrate that every claim involves encrypted systems. Responders should investigate data access, exposure, and system disruption separately.

    What should we do if we receive a 0x00 extortion demand?

    Keep the original message, attachments, and timestamps for your incident response team. Investigate the systems and information referenced, preserve relevant logs, and address any confirmed unauthorized access. Do not assume the demand accurately describes what happened.

    Can Alvaka help with data extortion if our systems are still working?

    Yes. Alvaka can assist with technical investigation, exposure assessment, containment, and attacker removal even when there is no widespread encryption. If services are disrupted, recovery options can be evaluated alongside the investigation.

    Contact Alvaka for 0x00 Ransomware Recovery Services

    If your organization has received a 0x00 extortion demand or identified suspicious activity, Alvaka can help assess the evidence and coordinate response and recovery.

    Our ransomware response and recovery team is available 24/7, 365 days a year.

    Contact Alvaka for emergency ransomware assistance.

  • What Happens When the Person Who Knows Your IT Environment Leaves?

    What Happens When the Person Who Knows Your IT Environment Leaves?

    Most organizations know they shouldn’t rely on one person for an entire business function.

    But IT has a way of becoming the exception.

    Over time, one employee may become the person who knows how everything works. They know the passwords. They know why a server was configured a certain way. They know which vendor to call, where the backups live, how the network is connected, which systems depend on each other, and which temporary fix quietly became permanent three years ago.

    Then one day, they’re gone. Maybe they accepted another job. Maybe they retired. Maybe they were terminated. Maybe they’re sick or unexpectedly unavailable. The reason almost doesn’t matter.

    The question is: Can your business still operate without them?

    Your IT Environment Should Belong to the Company, Not One Person

    The problem isn’t having a highly knowledgeable IT employee. Good IT professionals naturally accumulate enormous amounts of knowledge about the environments they manage. The problem is when that knowledge exists only with them.

    Leadership should be able to access critical systems and accounts without relying on a single employee. Important technology accounts should be controlled by the company, emergency credentials should be independently accessible, and critical systems should have more than one person capable of administering them. Organizations should identify technical roles that have become single points of failure and establish clear succession plans and decision-making authority before those individuals become unavailable.

    If your IT administrator disappeared tomorrow, would anyone else know how to get into Microsoft 365? Your cloud environment? Firewall? Backup system? Domain registrar? DNS? Security tools? If the answer is “I think so,” that’s worth investigating.

    The Password Isn’t the Only Thing You’re Losing

    This is where organizations can underestimate the problem. Giving another employee an administrator password doesn’t transfer years of institutional knowledge. A critical IT employee may understand:

    How systems depend on one another. Changing one service account or password could unexpectedly break an application, scheduled task, backup, or integration.

    Where everything actually is. Servers, cloud resources, network devices, applications, software licenses, VPNs, storage, certificates, public IP addresses, and specialized equipment all need to be inventoried and understood.

    Why things were configured a certain way. Temporary fixes, technical debt, exceptions, unsupported systems, scripts, automations, and known problems often live in someone’s memory rather than formal documentation.

    Who to call when something breaks. Vendor contacts, account numbers, support agreements, contracts, renewal dates, escalation paths, and service relationships can become tied to an individual employee.

    Losing the employee can mean losing pieces of all of the above at once.

    The Bigger Question: Who Actually Controls Your Technology?

    There’s another problem that’s potentially even more serious than missing documentation. Does the company actually control its own accounts? Critical technology accounts should be registered to the company, with company-controlled administrative email addresses, recovery methods, billing information, MFA, and multiple authorized representatives where possible. An employee’s personal email address, phone number, authenticator, credit card, password vault, or developer account should not be the thing standing between your organization and its own infrastructure. That applies to much more than Microsoft 365.

    Think about your:

    • Cloud infrastructure
    • Domain registrar and DNS
    • Website and hosting
    • Backup environment
    • Security tools
    • CRM and ERP
    • Telephony
    • Source code
    • Certificates
    • Software licensing
    • SaaS applications
    • Vendor and support portals

    One critical question organizations should ask is: Can an authorized executive prove ownership and regain control of every critical account without the employee?

    Every CEO should know the answer.

    “We Have Backups” Isn’t Enough Either

    Imagine discovering that your backups are working perfectly, but the only person who knows how to access the backup console just left.

    Or the encryption keys are tied to their credentials.

    Or the recovery documentation is on their laptop.

    Or nobody else has ever actually performed a restoration.

    That’s still a continuity problem.

    Organizations should know what is being backed up, who can independently access those backups, where encryption keys and recovery documentation are stored, and whether a complete recovery has actually been tested.

    A backup strategy shouldn’t depend on the availability of the person you’re trying to operate without.

    Planned Departures Are the Easy Version

    If someone gives two weeks’ notice, you have an opportunity to transfer knowledge, validate documentation, change ownership, test access, and create a deliberate transition.

    You don’t always get that opportunity.

    An employee can become immediately unavailable because of illness, an emergency, a walkout, termination, or another unexpected event. Organizations should ensure another qualified individual can assume administrative responsibilities using company-owned accounts, devices, documentation, and tools without relying on the unavailable employee.

    That’s the scenario businesses should prepare for.

    And if a departure is hostile or high-risk, the situation becomes a cybersecurity issue as well as an HR issue.

    Access may need to be revoked across user accounts, privileged accounts, active sessions, VPNs, API tokens, SSH keys, certificates, MFA methods, vendor portals, physical facilities, and more, while preserving evidence and avoiding changes that inadvertently break critical systems.

    It’s important to distinguish between routine employee offboarding and potential security threats. Evidence of sabotage, credential theft, unauthorized access, data removal, extortion, or concealment should be treated as a security incident, not a standard offboarding procedure.

    The Best Time to Find Out Is Before They Leave

    There is a simple exercise leadership can perform:

    Pick the person with the most knowledge and access in your IT environment and imagine they don’t come to work tomorrow.

    Don’t call them.

    Don’t ask them where something is.

    Don’t use their phone for MFA.

    Don’t rely on a password saved in their browser.

    Could your team still:

    • Access every critical system?
    • Restore from backup?
    • Administer Microsoft 365 and cloud environments?
    • Control your domains and DNS?
    • Contact and authenticate with critical vendors?
    • Find accurate network and system documentation?
    • Understand application dependencies?
    • Revoke privileged access?
    • Keep critical business systems running?
    • Recover from an outage?

    If you’re unsure about several of those answers, you’ve identified a business continuity risk.

    And this shouldn’t be based on someone’s assurance that “we have all of that covered.” Organizations should hold themselves to a higher standard:

    Could leadership prove, with evidence, that the organization could operate safely tomorrow if its IT leadership suddenly became unavailable?

    Don’t Wait for a Resignation to Test Your IT Continuity

    Your most knowledgeable IT employee can be an enormous asset. They shouldn’t also be a single point of failure.

    Whether you have an internal IT team, an existing MSP, or a combination of both, your organization needs independent visibility, documentation, and technical support to ensure critical systems remain operational when key personnel become unavailable.

    That’s where Alvaka can help.

    We work alongside existing IT teams to strengthen infrastructure monitoring, documentation, security, backups, and recovery capabilities. Our U.S.-based team provides support 24/7, 365 days a year, giving organizations an additional layer of technical expertise and continuity when internal resources change.

    The goal isn’t to replace a great IT employee. It’s to make sure your business can continue operating without depending entirely on one person.

    If you’re unsure whether your organization has that level of resilience, Alvaka can help identify critical dependencies and address potential gaps before they lead to business interruptions.

    Talk with Alvaka about your IT enviornment.

  • UmBra Ransomware Recovery Services

    UmBra Ransomware Recovery Services


    What Is UmBra?

    UmBra is a threat group associated with public extortion claims against organizations in industries including education, technology, and manufacturing.

    An UmBra-related extortion claim warrants an investigation into whether unauthorized access occurred, what information or systems may have been compromised, and whether any attacker access remains active.

    Although public victim listings can help organizations identify emerging threats, those claims should be evaluated against technical evidence before conclusions are drawn about the nature or extent of an incident.

    UmBra Victims and Targeted Industries

    Public ransomware intelligence sources have associated UmBra with claimed victims across North America, South America, Africa, Asia, and the Middle East.

    Organizations appearing in public tracking include Four Hands, a U.S. furniture and home furnishings company, and Beni Suef Technological University in Egypt.

    These listings illustrate the range of organizations named in UmBra-related reporting but do not independently confirm successful breaches.

    For affected organizations, the potential consequences extend beyond data security. Manufacturers may experience production delays, educational institutions may lose access to administrative systems, and businesses handling sensitive customer information may face extensive exposure assessments.

    How UmBra-Related Incidents Are Investigated

    When an organization receives an UmBra extortion demand or discovers suspicious activity associated with the group, the priority is establishing what occurred within its environment.

    An effective investigation may involve:

    • Authentication and remote access analysis: Reviewing VPN, remote desktop, and identity-provider logs for suspicious sessions, unauthorized account use, or unexpected privilege changes.
    • Endpoint and server examination: Investigating unusual processes, unauthorized tools, system modifications, and evidence of attacker persistence.
    • Data exposure assessment: Examining access to sensitive repositories, unusual archive creation, bulk downloads, and outbound data transfers.
    • Infrastructure and backup evaluation: Determining whether critical applications, servers, identity systems, or recovery resources have been affected.

    These investigative steps help responders establish the scope of an incident, identify remaining threats, and determine the appropriate containment and recovery measures.

    Potential Business Impact of an UmBra Incident

    A ransomware or extortion incident can create serious operational challenges even without widespread file encryption.

    Sensitive Data Exposure

    Unauthorized access to confidential business information, employee records, customer data, or proprietary documents may require an extensive investigation and legal or regulatory assessment.

    Business Interruption

    Compromised infrastructure can disrupt employee access, critical applications, customer-facing services, and daily operations. Extended downtime can increase recovery costs and affect customer and business relationships.

    Compromised Credentials and Persistent Access

    Attackers may retain access through compromised accounts or unauthorized remote-access tools, leaving an organization exposed even after the initial suspicious activity has stopped.

    Recovery Complications

    Affected identity infrastructure, damaged systems, or unavailable backups can complicate restoration. Returning applications to service before confirming that attacker access has been eliminated may introduce additional risks.

    Alvaka’s UmBra Ransomware Response and Recovery Services

    Alvaka provides specialized ransomware response and recovery services, helping organizations investigate suspected compromises, contain active threats, and restore critical IT infrastructure.

    Our team works alongside internal IT departments to identify unauthorized access, assess potential data exposure, eliminate attacker persistence, and recover affected systems. With extensive experience handling complex ransomware incidents across healthcare, manufacturing, education, government, and other industries, Alvaka understands the urgency of restoring operations while reducing the risk of further compromise.

    Frequently Asked Questions About UmBra

    What is UmBra ransomware?

    UmBra is a threat name appearing in ransomware and cyber extortion intelligence reporting. Organizations associated with UmBra-related claims should investigate whether unauthorized access, data exposure, or operational compromise has occurred.

    What industries has UmBra targeted?

    Public tracking has included claimed victims in education, technology, manufacturing, and other industries across multiple geographic regions. The presence of an organization on a claimed-victim list does not independently establish a confirmed breach.

    What should I do if UmBra claims to have compromised my organization?

    Preserve the extortion communication and any supporting evidence, involve your incident response team, and investigate the affected environment. Avoid assuming that the attacker’s claims accurately describe the scope of the incident.

    Can Alvaka help if our files have not been encrypted?

    Yes. Cyber extortion incidents can involve suspected unauthorized access or data exposure without widespread encryption. Alvaka can help investigate the environment, assess technical evidence, and address confirmed security issues.

    Can Alvaka recover systems affected by ransomware?

    Alvaka provides ransomware recovery services that may include infrastructure rebuilding, backup evaluation, system restoration, and recovery of critical applications. Available recovery options depend on the condition of the affected environment and its recovery resources.

    Contact Alvaka for UmBra Ransomware Recovery Services

    If your organization has received an UmBra extortion demand, appeared in a claimed-victim listing, or discovered suspicious activity, Alvaka can help investigate the incident and determine the appropriate response.

    Our ransomware response and recovery team is available 24/7, 365 days a year.

    Contact Alvaka for emergency ransomware assistance.

  • Adding AI to Your Healthcare Practice? Your HIPAA Risk Analysis May Need an Update

    Adding AI to Your Healthcare Practice? Your HIPAA Risk Analysis May Need an Update

    Artificial intelligence is quickly becoming part of everyday operations in healthcare. AI-powered tools are being introduced for everything from documentation and scheduling to patient communication, marketing, analytics, administrative workflows, and clinical support. But there is an important question that healthcare organizations should be asking as they adopt these tools:

    How does this change our HIPAA security risk?

    If an AI tool creates, receives, maintains, or transmits electronic protected health information (ePHI), or changes how that information is accessed or handled within your organization, it may introduce risks that need to be considered as part of your HIPAA Security Rule risk analysis. And that conversation applies to far more organizations than just hospitals.

    Who Are We Talking About?

    When people hear “healthcare cybersecurity,” they often picture large hospitals and health systems. But HIPAA can apply across a much broader healthcare ecosystem. Depending on the services provided, information handled, and whether the organization qualifies as a HIPAA covered entity or business associate, this conversation may include:

    • Medical practices and physician groups
    • Med spas and aesthetic practices
    • Dental and orthodontic practices
    • Physical therapy and rehabilitation centers
    • Podiatry practices
    • Ophthalmology and other eye care practices
    • IV hydration and wellness clinics
    • Behavioral health and therapy centers
    • Specialty clinics
    • Diagnostic and imaging centers
    • Home health organizations
    • Other healthcare organizations and their business associates that create, receive, maintain, or transmit ePHI

    If your organization falls into one of these categories, adding a new AI platform isn’t simply a productivity decision. It can also change the environment in which sensitive patient information is being handled.

    AI Adoption Can Change Your Risk Environment

    A HIPAA risk analysis isn’t meant to be something an organization completes once and forgets about. Under the HIPAA Security Rule, covered entities and business associates are required to conduct an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity, and availability of ePHI. That means understanding where ePHI exists, who and what can access it, what threats and vulnerabilities exist, what safeguards are already in place, and the potential likelihood and impact of those risks.

    Introducing new technology can change that picture. An AI tool may introduce a new vendor, new integration, new user permissions, new data flows, or an entirely new location where information is processed or stored. That doesn’t mean healthcare organizations shouldn’t use AI. It means AI adoption should happen with an understanding of what the technology is actually touching.

    Start by Understanding What Your AI Actually Touches

    Before implementing an AI tool, healthcare organizations should understand how it interacts with their existing environment.

    Questions worth asking include:

    • What information is being entered into the AI system?
    • Does that information contain ePHI?
    • Where is the information processed and stored?
    • Who has access to it?
    • Does the AI platform integrate with your EHR, CRM, scheduling platform, email, cloud environment, or other systems?
    • Does the vendor retain information submitted to the platform?
    • Is submitted information used to train or improve models?
    • What security controls are available?
    • Does the vendor need to function as a HIPAA business associate, and if so, is an appropriate Business Associate Agreement in place?

    The answers can be very different from one AI product to another. That’s why simply saying an application “uses AI” doesn’t tell you much about its actual security or HIPAA implications.

    When Was Your Last HIPAA Security Risk Assessment?

    If your organization hasn’t recently completed a HIPAA security risk assessment, HHS provides a resource that can help. The Security Risk Assessment (SRA) Tool, developed by the Office of the National Coordinator for Health Information Technology in collaboration with the HHS Office for Civil Rights, was designed to help small and medium-sized healthcare practices and business associates assess security risks. The important distinction we wanted to make here is: The assessment identifies the risks. The next question is what you’re going to do about them.

    Finding the Risk Is Only the Beginning

    A risk assessment may reveal outdated systems, inadequate access controls, missing MFA, insufficient network segmentation, backup weaknesses, patching problems, unsupported technology, poor visibility, or other technical vulnerabilities. Identifying those issues is important. Remediating them is where the technical work begins. And as healthcare organizations introduce AI into more areas of their operations, understanding the relationship between those new technologies and the rest of the environment becomes increasingly important.

    Where Alvaka Can Help

    Alvaka can help healthcare organizations address the technical side of the risks identified through their security assessments. That can include evaluating existing security controls, identifying technical vulnerabilities, improving patching and system management, strengthening backup and recovery capabilities, improving visibility into the environment, and implementing cybersecurity safeguards designed to reduce operational risk. And because Alvaka also responds to ransomware incidents, our team sees what happens when weaknesses in real-world environments are successfully exploited. That experience informs how we approach prevention, resilience, and recovery.

    AI Adoption Doesn’t Have to Mean Uncontrolled Risk

    Healthcare organizations don’t need to choose between adopting AI and protecting sensitive information. But new technology should not be introduced without understanding how it changes the organization’s security environment. If your practice is implementing new AI tools, integrating AI into existing systems, or simply hasn’t revisited its HIPAA security risk analysis recently, now may be the right time to take another look. Understanding where your information lives, how it moves, who can access it, and what new technologies interact with it is an important part of protecting both your patients and your organization.

  • AI Is Changing Who Is Worth Attacking: Why Smaller Businesses Need to Rethink Cybersecurity

    AI Is Changing Who Is Worth Attacking: Why Smaller Businesses Need to Rethink Cybersecurity

    Written by Sarah Accongio, Market Development Specialist at Alvaka

    For years, many smaller businesses have operated under an assumption that quietly shaped their cybersecurity decisions: Why would a ransomware group bother with us?

    A regional dental practice is not a Fortune 500 company. Neither is a growing medspa, a 40-person law firm, an accounting practice, a property management company, or a regional manufacturer. But that may increasingly be the wrong question.

    Artificial intelligence is changing the economics of cybercrime. As attackers automate more of the work traditionally performed by people, the amount of time and manpower required to target an organization can decrease. And if attacking a business becomes faster and cheaper, the business does not necessarily need to represent an enormous payday to become worth attacking.

    How Is AI Changing Cyberattacks?

    Cybercriminals face the same constraint every legitimate business does: labor. Finding potential victims, researching employees, scanning infrastructure, identifying vulnerabilities, creating convincing phishing messages, harvesting credentials, maintaining attack infrastructure, and troubleshooting failed attempts all require time.

    AI is beginning to change that equation.

    Google Threat Intelligence Group (GTIG) recently reported that threat actors are progressing from basic AI prompting toward agentic AI workflows and AI-enabled automation. In one financially motivated operation observed in 2026, an attacker compromised cloud infrastructure and then used an AI-enabled framework to plan, build, and execute a mass credential-harvesting campaign in less than six hours. The framework could autonomously manage vulnerability scanning, troubleshoot problems, rotate IP addresses, and harvest credentials with substantially less human intervention. Thousands of third-party credentials were compromised.

    That represents an important shift. AI is not simply helping an attacker write a better phishing email. It is beginning to automate portions of the attack process itself.

    For defenders, that can mean less time to recognize and stop an attack. For smaller businesses, it may mean something else too:

    You may be becoming a more economical target.

    Are Smaller Businesses Becoming Bigger Ransomware Targets?

    Smaller and mid-sized organizations are already significant ransomware targets. Black Kite’s 2026 Mid-Market Ransomware Report analyzed 13,336 disclosed ransomware and extortion incidents with verifiable revenue across North America and Europe between January 2023 and June 2026. It found that 73% involved organizations earning between $10 million and $1 billion annually.

    Within that group, businesses earning just $10 million to $50 million represented the largest portion of victims every year studied. Separate Black Kite research also found that the $1 million to $5 million revenue segment nearly doubled its share of ransomware victims in its latest reporting period.

    The idea that ransomware is primarily a big-enterprise problem is increasingly difficult to defend. And AI could push that economics further down-market.

    We should be careful about what the evidence does and does not tell us. We cannot yet say that AI is causing ransomware groups to systematically move toward every category of small business. But we can make a reasonable prediction based on what is changing:

    As AI reduces the human effort required to identify, research, and attack potential victims, organizations that once appeared too small to justify an attacker’s time may become increasingly attractive targets.

    Which Smaller Businesses Should Be Paying Attention?

    Consider a growing medspa. It may have started with a single injector and grown into a multimillion-dollar operation with employees, multiple locations, patient records, photographs, payment information, email accounts, cloud applications, and regulated health information.

    To its owner, it may still feel like a small business. To an attacker, it may look like valuable data, meaningful revenue, operational dependence on technology, and a relatively small IT/security operation protecting all of it.

    The same logic applies to dental and orthodontic practices. A ransomware incident can affect patient records, imaging, scheduling, billing, and the systems required to operate the practice. But this extends far beyond healthcare.

    Law firms possess privileged communications, financial records, litigation strategy, intellectual property, and sensitive client information. Accounting and bookkeeping firms may have tax returns, Social Security numbers, payroll information, banking information, and access to client financial systems.

    Title, escrow, mortgage, and real estate businesses combine sensitive personal information with large and time-sensitive financial transactions. Property management companies hold tenant data, payment information, leases, banking details, vendor information, and increasingly connected property systems.

    Manufacturers may have less regulated personal data, but downtime itself creates tremendous leverage. If systems are unavailable and a company cannot manufacture, fulfill orders, or ship products, every hour can have a measurable cost.

    Construction companies, veterinary practices, insurance agencies, logistics providers, architecture and engineering firms, auto dealerships, private schools, and many other growing businesses share some combination of the same characteristics. They have something valuable to steal, something important to disrupt, and fewer cybersecurity resources than a large enterprise.

    The ransomware data already reflects much of this. Manufacturing represents 25.8% of the mid-market victims in Black Kite’s dataset, followed by professional and technical services and construction. Healthcare, wholesale, information, and education also appear among heavily affected sectors.

    Small Doesn’t Mean Invisible Anymore

    AI is not necessarily creating an entirely new cybersecurity problem. In many cases, it is allowing attackers to find and exploit the security problems businesses already had, only faster and at greater scale.

    An old employee account that was never disabled.

    A remote-access system without multifactor authentication.

    An unpatched internet-facing device.

    A password reused across accounts.

    An employee who receives an extremely convincing email appearing to come from an executive or vendor.

    A backup environment accessible with credentials connected to production.

    A malicious message that reaches an employee’s inbox.

    Poorly controlled administrative privileges.

    Those weaknesses mattered before generative AI. The difference is that attackers are gaining better tools for finding and exploiting them.

    That makes basic cybersecurity discipline more important, not less.

    You Don’t Need an Enterprise Security Budget. You Need Security Discipline.

    A 30-person company does not need to replicate the cybersecurity department of a multinational corporation. It does need to stop treating cybersecurity as something that can wait until the company becomes bigger.

    CISA’s guidance for small and medium-sized businesses emphasizes fundamentals including phishing protection, strong passwords, multifactor authentication, software updates, logging, backups, and encryption. Its ransomware guidance specifically recommends phishing-resistant MFA for email, VPNs, and accounts that access critical systems, as well as offline, encrypted, regularly tested backups.

    For smaller organizations, we believe several areas deserve particular attention.

    Protect identity. Require MFA wherever possible, particularly for email, remote access, administrators, and systems containing sensitive information. Remove stale accounts, limit administrative privileges, and make sure access disappears when an employee or vendor no longer needs it.

    Protect email. Email remains an important point where technology and human trust intersect. Organizations should use layered email security capable of identifying malicious messages, impersonation attempts, suspicious links, and other threats before they reach employees. Solutions such as Alvaka’s Mailworx can add another layer of protection around one of the most frequently used business communication systems.

    Patch what attackers can see. Know which systems are exposed to the internet and establish a repeatable vulnerability and patch-management process. A critical vulnerability should not sit unnoticed because nobody knew which system was responsible for it. Alvaka’s Patchworx helps organizations maintain the patching discipline necessary to reduce that exposure.

    Monitor the environment. As attack timelines shrink, relying on someone to manually notice suspicious activity becomes increasingly dangerous. Continuous monitoring and managed detection can help identify abnormal behavior before an attacker has had days to operate unnoticed. This is part of the reason Alvaka developed ODIN 360 around ongoing visibility, monitoring, and protection.

    Protect your ability to recover. Backups should be protected from the same credentials and systems attackers may compromise. They should also be tested. Finding out during a ransomware incident that a backup is inaccessible, incomplete, or encrypted is too late.

    Create verification procedures. Employees should know that familiarity is no longer proof of authenticity. An email that sounds exactly like the CEO, a message written perfectly in a vendor’s normal style, or even convincing audio should not override established procedures. Requests involving money, credentials, sensitive data, or unusual access should have an independent verification process.

    What Does Safe AI Adoption Look Like for a Small Business?

    There is another side of this conversation that matters just as much.

    The answer is not to stop using AI.

    AI can give a smaller organization capabilities that previously required a much larger staff. It can help employees analyze information, automate repetitive work, improve customer service, create content, write software, and operate more efficiently. Businesses should absolutely be exploring those opportunities.

    But AI adoption and cybersecurity cannot be treated as two separate initiatives. GTIG has also observed attackers targeting AI assets themselves, including proprietary models, source code, prompts, API credentials, and cloud computing resources.

    As businesses adopt AI, they need to know:

    • What AI tools are employees using?
    • What customer, patient, financial, or proprietary information are employees allowed to enter into those tools?
    • Who has access to company AI accounts?
    • Where are API keys and credentials stored?
    • Are AI-generated code and automations reviewed before being deployed?
    • What happens when an employee leaves?
    • Are third-party AI vendors being evaluated before sensitive information is shared with them?

    And perhaps most importantly: Does adopting AI introduce a new connection to data or systems that nobody on the security side knows exists?

    Shadow AI can become the next version of shadow IT.

    The goal should not be to prevent employees from using transformative technology. The goal should be to adopt it intentionally, with security controls developing alongside the technology rather than years behind it.

    Protect Your Business From AI While Learning to Use It Safely

    Small businesses are being presented with an enormous opportunity. AI can allow a 20-person company to operate with capabilities that once required a much larger organization.

    But the same economic advantage is becoming available to the people trying to attack it.

    That means business owners should be asking two questions at the same time:

    How can we use AI to make our company better?

    How do we make sure AI doesn’t make us easier to attack?

    The answer to the second question does not begin with some futuristic AI security product. It starts with the fundamentals.

    Protect identities. Secure email. Patch vulnerabilities. Monitor systems. Segment access. Protect and test backups. Train employees to verify unusual requests. Know where sensitive information lives. Understand which AI tools are being used inside the organization.

    And have a plan for what happens if those defenses fail.

    The businesses that benefit most from AI won’t necessarily be the ones that adopt it the fastest. They’ll be the ones that learn how to use it without abandoning the security practices protecting everything they’ve built.

    At Alvaka, we help organizations strengthen those fundamentals, monitor their environments, reduce exposure, and prepare for the incidents they hope never happen.

    Because as attackers become faster and more automated, being “too small to target” is not a security strategy.

  • Cyber Criminal Unemployment? Something to Celebrate in the Unnerving Google GTIG Report

    Cyber Criminal Unemployment? Something to Celebrate in the Unnerving Google GTIG Report

    Written by Kevin B. McDonald, COO & CISO at Alvaka

    The Question Everyone Is Asking About AI

    Understandably and rightfully, AI aware humans are genuinely concerned about AI replacing them and diminishing their value in the commercial marketplace. Many developers are sitting on the edge of their seat, wondering when AI development will fully replace them. Writers are seeing people who could not construct complete sentences putting out materials that on the surface seem well informed and insightful. Analysts are worried that machines can read a million times more data points and draw correlations is seconds that a typical human could spend a lifetime working toward. It seems that every business conference, podcast, publication, and LinkedIn thread no matter the vertical revolves in some way around the same question. 

    Who’s getting replaced by Artificial Intelligence and what then?

    What About the Cybercriminal Workforce?

    After reading Google’s latest GTIG report, I found myself thinking a lot about a different “workforce” that has a real problem, unless they start their own operations from the ground up.  

    Cybercriminals who are simple affiliates or specialists in activities that can be replicated by AI consistently. 

    This is certainly a possibility, but entrepreneurial behavior is unusual, so it is likely that many will just not see future criminal opportunity. For years, ransomware, BEC operations and other cybercrime groups have been operated like a business. My decades of experience shows in fact that some of cybercriminal syndicates are better organized, better funded and more “professional” and effective than far too many legitimate businesses. Of course, cybercriminals are not ethical businesses, but businesses, nonetheless. Much of what holds the hacker and cybercriminal ecosystem together is specialized and unique skills that are (or were) difficult to replicate.  

    Cybercrime Has Its Own Supply Chain

    One group specializes in access and breaking into organizations’ systems. They phish users, steal credentials, exploit vulnerabilities, and plant persistent access. Then they sell that access to the next specialist in the supply chain. The next link in the chain buys access and deploys a myriad of criminal playbooks inside victim environments. While all this is going on yet another group develops the ransomware, builds delivery infrastructure and vets affiliates and finally there are still more that do negotiations and collect the cash. 

    Everyone gets a piece of the proceeds and supply chains work because different people perform different jobs effectively. 

    AI Could Disrupt the Cybercrime Business Model

    Google’s report suggests that like other industries, something important is changing in the cybercrime world. Threat actors are moving beyond using AI for individual tasks and experimenting with fully autonomous workflows. AIs now perform larger portions of the supply chain with less human involvement. The report also calls out that the crooks are increasingly targeting AI infrastructure, the models themselves, source code, and more. 

    Most will read all of this and think about faster phishing emails, easier deployment, etc. I think there is a bigger story to celebrate. What happens to an irrelevant access broker? Why pay a human to find vulnerable systems when an AI agent can do it continuously, at greater speed and at a superhuman scale? Why pay to validate credentials or spend days mapping a network when an agent can do it more accurately in hours? 

    Could AI Create Cybercriminal Unemployment?

    Despite all the high-tech headlines, most traditional cybercrime takes people. People create problems. They make mistakes, get lazy, disappear and get arrested.  Any group of people can have potential conflicts and otherwise create friction. AI removes human fallibility and friction. We know this worries defenders and it should. But it should also worry criminals that are just cogs in the machine.  Productivity tools may end up creating unemployment in the cybercrime economy. 

    Ironically, the criminals who spent years perfecting everyone else’s misery may soon find themselves competing with automation itself. 

    What Happens When the Criminals Become the Cogs?

    I have often said that ransomware groups are some of the most entrepreneurial organizations on the planet. They have built franchises, complex and functional partner programs, revenue sharing models, effective support desks, service delivery teams, and recruiting processes. They have created an entire underground employment marketplace. 

    If AI can perform your criminal function with less drama for less money, faster, and around the clock, what exactly is an affiliate’s role? Less humans in a criminal conspiracy means less risk. More AI means the top-level operators keep more of the pie. So, only time will tell if we see more or less criminal actors and whether AI actually helps to take down the criminal economy on a broader scale. 

    What Executives Should Do Now

    1. Prepare for fewer attackers but more attacks: Don’t assume shrinking criminal workforces means less risk. AI may allow fewer operators to generate significantly more attacks.
    2. Adjust threat models for automation: Many security programs still assume human adversaries with limited capacity. Plan for advanced adversaries operating continuously, at scale, and around the clock.
    3. Invest in security speed, not just security controls: Faster detection, faster decisions, and faster containment are becoming more important than adding another point solution.
    4. Expect more sophisticated attacks at lower cost: As criminal operations automate, the cost of launching campaigns may fall dramatically.
    5. Increase monitoring of identity and cloud resources: Identity remains the most valuable target.
    6. Track AI-enabled changes in criminal behavior: Security teams should monitor how attacks are changing, not just how technology is changing.
    7. Build security automation carefully: Criminals are automating aggressively. Defenders need automation too, but with governance, oversight, and testing.
    8. Protect AI assets as business assets: Treat models, prompts, APIs, source code, training data, and cloud infrastructure as critical assets.

    Bottom Line

    AI may not eliminate cybercrime. It may eliminate cybercriminal jobs. If that happens, organizations should expect leaner, faster, cheaper, and more scalable attacks. The winning strategy will be building defenses that operate at the speed of the threat, not the speed of traditional security operations.

  • Cisco CVE-2026-20079 Is Being Actively Exploited: What Organizations Need to Know

    Cisco CVE-2026-20079 Is Being Actively Exploited: What Organizations Need to Know

    Cisco has confirmed active exploitation of CVE-2026-20079, a maximum-severity authentication bypass vulnerability affecting Cisco Secure Firewall Management Center (FMC) Software.

    The vulnerability carries a CVSS score of 10.0 and allows an unauthenticated remote attacker to bypass authentication and obtain root access to an affected device. Cisco first disclosed the vulnerability in March 2026, and active exploitation has now been confirmed.

    For organizations using Cisco Secure FMC, this has moved beyond a vulnerability-management issue. Active exploitation means organizations should be evaluating both patch status and the possibility that compromise has already occurred.

    What Is CVE-2026-20079 and Why Is It Critical?

    CVE-2026-20079 is a critical authentication bypass vulnerability in Cisco Secure FMC that can allow an unauthenticated remote attacker to execute commands with root privileges on an affected device.

    The vulnerability exists in the web interface of Cisco Secure FMC Software and, according to Cisco, is caused by an improper system process created at boot time.

    An attacker can exploit the flaw by sending crafted HTTP requests to an affected device. Successful exploitation can provide root-level access to the underlying operating system without requiring authentication.

    That level of access to security infrastructure is significant.

    Firewall management systems occupy a particularly sensitive position in an organization’s environment. Compromise can provide attackers with opportunities to collect information about network architecture, configurations and connected systems, steal credentials, establish persistence, and move deeper into the environment.

    Cisco notes that organizations whose FMC management interfaces are not publicly accessible have a reduced attack surface, but the underlying vulnerability still needs to be addressed.

    Is CVE-2026-20079 Connected to Ransomware?

    Yes. Cisco Talos has documented ransomware-related activity involving compromised FMC instances, including an intrusion that ultimately resulted in Qilin ransomware being deployed on selected endpoints.

    Talos is tracking multiple clusters of malicious activity involving compromised FMC instances.

    One cluster, tracked as UAT-11988, is assessed by Talos with high confidence to be a ransomware operator. The attacker abused FMC functionality for reconnaissance, deployed tunneling tools, harvested credentials, and built a target list of endpoints to encrypt or lock.

    The subsequent activity was consistent with Qilin ransomware affiliates, and Talos reports that Qilin ransomware was ultimately deployed on selected endpoints.

    A separate cluster, UAT-11823, exploited CVE-2026-20079 and CVE-2026-20316 and deployed reverse-shell and proxy tooling. Talos identified overlap with tooling associated with the Russian state-sponsored Sandworm APT, including a variant of Cyclops Blink, malware previously attributed to Sandworm by the United States and United Kingdom.

    A third cluster, UAT-12197, involved exploitation of CVE-2026-20079 followed by deployment of web shells, a Java-based command executor, and credential exfiltration.

    The important takeaway is not simply which threat group may be involved.

    The same vulnerable security infrastructure is attracting both crimeware and state-linked activity.

    Is Patching CVE-2026-20079 Enough?

    No. Patching is critical, but if an affected Cisco Secure FMC system was exploited before it was updated, applying the fix does not establish that the environment is clean.

    There is an important distinction organizations need to understand when responding to an actively exploited vulnerability:

    Closing the vulnerability prevents the same door from being used again. It does not prove nobody already walked through it.

    Cisco has released software updates and hot fixes for affected versions and states that there are no workarounds that address CVE-2026-20079.

    More importantly, Cisco warns that its hot fixes are intended to prevent future exploitation and may not address an existing compromise. If indicators of compromise are discovered, Cisco recommends contacting its Technical Assistance Center for recovery guidance.

    If an attacker obtained root access before a system was patched, the response cannot stop at installing an update.

    Organizations need to determine what the attacker accessed, what credentials may have been exposed, what persistence may have been established, whether other systems were reached, and whether additional malicious activity remains elsewhere in the environment.

    How Can You Tell If Cisco Secure FMC Was Compromised?

    Organizations should review Cisco’s published indicators of compromise and investigate affected FMC systems for evidence of unauthorized access, credential theft, persistence, tunneling, and lateral movement.

    Cisco has published an indicator administrators can use to determine whether exploitation may have occurred. Administrators can review FMC logs for activity involving:

    /var/tmp/license.tmp

    Cisco states that documented package_info activity involving this file may indicate exploitation.

    Cisco Talos has also published additional indicators and detection guidance associated with the activity it investigated, including Snort signatures for the vulnerabilities and associated malware.

    Organizations should also investigate unexpected authentication activity, configuration changes, credential use, tunneling or proxy activity, suspicious outbound connections, persistence, and evidence of lateral movement.

    Finding one compromised device should not automatically define the scope of the incident. If credentials or additional systems were accessed, investigation may need to extend well beyond the FMC appliance itself.

    The Ransomware Recovery Question

    The confirmed connection to ransomware makes the response particularly important.

    Talos documented attackers harvesting credentials, establishing tunnels into the victim environment, probing endpoints, using tools including Impacket and Invoke-TheHash, attempting to disable antivirus protections, and ultimately deploying Qilin ransomware on selected endpoints.

    That illustrates why an exploited security appliance cannot automatically be treated as an isolated incident.

    If investigation shows that attackers progressed beyond exploitation into credential theft, reconnaissance, lateral movement, persistence, or preparation for encryption, the organization may already be dealing with an incident rather than simply a vulnerable appliance.

    At that point, ransomware recovery and restoration decisions need to account for more than whether backups are available.

    Before systems are restored to production, organizations need confidence that attacker access has been removed, compromised credentials have been addressed, persistence mechanisms have been identified, and the restored environment is not being reconnected to infrastructure that remains compromised.

    Restoring systems without understanding the scope of the intrusion can return an organization to an operational state without returning it to a trusted state.

    What Security Teams Should Do Now

    Organizations using Cisco Secure FMC should:

    1. Identify affected FMC systems and software versions.
    2. Apply Cisco’s available hot fixes or upgrade to a fixed software release immediately.
    3. Determine whether FMC management interfaces are exposed to the public internet.
    4. Review Cisco’s published indicators of compromise.
    5. Review the additional IOCs and detection guidance published by Cisco Talos.
    6. Investigate for credential theft, persistence, reconnaissance, tunneling, and lateral movement.
    7. Treat evidence of compromise as an incident, not simply a patching exercise.
    8. If ransomware-related activity is discovered, establish the scope of compromise before beginning full restoration.

    Cisco Talos has also discussed a broader hardening release incorporating the existing hot fixes and fixes for other internally discovered vulnerabilities. Given the active exploitation, organizations should not delay applying currently available protections while waiting for future updates.

    When to Call Alvaka

    If you identify indicators of compromise, suspicious activity, or evidence that an attacker may have accessed an affected Cisco Secure FMC system, the situation has moved beyond vulnerability management.

    Alvaka can help organizations determine the scope of the intrusion, contain attacker access, identify persistence and compromised credentials, and assess whether other systems in the environment were affected.

    If the activity has progressed toward ransomware deployment, encryption, or widespread compromise, our team can also assist with ransomware incident response, recovery, and restoration, including helping determine whether systems are safe to return to production.

    The goal is not simply getting systems back online. It is making sure you are not restoring into an environment the attacker still controls.

    If you suspect CVE-2026-20079 has been exploited in your environment or you are dealing with an active ransomware incident, contact Alvaka immediately at (877) 662-6624.

    Bottom Line

    CVE-2026-20079 is no longer a theoretical risk.

    Cisco has confirmed active exploitation of this CVSS 10.0 authentication bypass vulnerability, while Cisco Talos has documented activity involving credential theft, persistence, tunneling, reconnaissance, and ransomware deployment. One investigated intrusion progressed to the deployment of Qilin ransomware, while another involved tooling overlapping with the Russian state-sponsored Sandworm APT.

    Organizations running affected Cisco Secure FMC software should patch immediately, but they should not assume patching answers the more important question:

    Was the system already compromised?

    For an actively exploited vulnerability with root-level impact, answering that question is just as important as closing the vulnerability itself.

  • The AI Threat Nobody Wants to Talk About

    The AI Threat Nobody Wants to Talk About

    Written by Kevin B. McDonald, COO & CISO at Alvaka

    The Real Shift: AI Is Becoming the Operator

    Like so many recent reports, Google’s latest GTIG report on adversarial AI should make executives, security leaders, and MSPs uncomfortable. Not because criminals are using AI. We already knew that. Not because phishing emails are getting better. We knew that too. The real story is about cybercriminals abandoning manual work and potentially shrinking the entire cybercrime ecosystem.  

    For the last few years, most discussions around AI in business and cybercrime have focused on productivity. We have all acknowledged that threat actors write phishing emails, research victims, find vulnerability, and create malware faster. These are all a growing list of threats causing us to collectively lose sleep. What Google’s GTIG report discusses is something different. 

    Attackers are no longer treating AI as a tool for human operators to use. They are beginning to use AI as the operator itself. 

    According to the report, cyber criminals are fast moving from simple prompting and code help to autonomous agentic workflows. These systems can now act, solve problems, adapt to obstacles in real time and reach objectives with limited to no human involvement.  

    What an AI-Driven Attack Looks Like in the Real World

    I have seen the results of advanced AI deployment firsthand. A victim contacted me and explained that their finance team had been hit with a $1.5 Million BEC attack. They were very sophisticated and well aware of the common risks. Their vendor’s email account is believed to have been hacked by AI phishing. It then reviewed the emails in the vendor’s account and identified an invoice that was coming due. The AI then drafted an email to the victim customer in the tone and email “voice” of the vendor finance person. This is someone the victim frequently communicated with. The email came from a legitimate account, reminding the victim of the real debt and that a final reminder would be coming in a few days and new account information would be included. The sender’s signature salutation was unique and something only the usual sender would say.

    Days later, the victim received the promised reminder email with a note to enter new account information in the vendor’s official portal that the victim commonly used. In the email was an invoice and embedded link to a website with a highly similar web address. The victim clicked the payment link as was traditional between the two companies. I must note that the victim acknowledged that she had concerns about changing the account information, but started the payment process anyway because everything felt normal. When she clicked the link, it took her to a website that was a flawless complete duplication of the vendor’s complex website. The victim clicked around, and the pages looked, acted and, most importantly, felt normal to her. All of the details she looked at down to the contact section, chat bot, and other functions were what she was used to seeing. The victim felt confident she had verified the site and went through the payment process and included the new banking information for the pay to account.

    It was only after she received an email notice of non-payment a couple days later that she realized something was terribly wrong. To make a long story short, the attack from initial compromise to, website replication and the financial transaction is estimated to have happened in about 72 hours. Thankfully, we were able to assist them in a nearly miraculous recovery (as so much time had passed) with the help of federal law enforcement. This could have been avoided by a phone call, but we all operate in the familiar and many have said to me, I don’t want to look paranoid. Please be paranoid, make the call. Do not trust what you see or hear. Do not trust any incoming communication you did not initiate.

    Attack Timelines Are Collapsing

    Yes, 72 hours seems ludicrous but Google shares in their report, one example where adversaries reportedly compromised cloud resources and planned, built, and executed a credential harvesting attack in less than six hours. A reality we all face is that attack cycles continue to gain sophistication and shrink timelines in ways we could not have imagined just a few months ago. We defenders are still operating on human timelines. 

    Companies need incident response systems, processes and time for investigations. We need people or systems to catch the actions, review alerts, and make decisions. Threat actors are increasingly building systems that do not need any of these time wasting steps, because the risk of damage is not theirs. Worst case for them, the Ai causes destruction and they fail to get paid.  

    A key takeaway from this report is not that AI is just becoming smarter. AI is becoming faster than many organizations can reasonably detect and respond effectively. 

    AI Is Becoming a Target, Too

    Our industry has spent years discussing how AI could help businesses and was a threat to traditional security. Far less attention has focused on AI assets and Google calls this out. Model weights, proprietary prompts and guardrails, research, source code, API credentials, and cloud compute are examples of valuable targets being sought by cybercriminals’ AI.  

    One of my greatest frustrations as a cyber defender is organizations rushing to build AI capabilities without deep consideration of how those systems will be protected. Tech history tells us that never ends well. Many executives have convinced themselves that AI coding tools somehow improve security. In reality, they are proven to create less secure code and a greatly expanded attack surface. Every automation becomes another layer that can be accessed and manipulated. 

    We Are Repeating an Old Security Mistake at AI Speed

    I have written extensively on the same pattern repeated for decades. We introduce new technologies for efficiency and features before security. Cybercriminals learn how to exploit vulnerability, defenders implement controls, and the criminals adapt yet again. The difference now is the speed of adaptation. AI is hyper accelerating it. 

    Too many organizations do not know where their AI systems are or how they are being used. They do not know what employees are connecting to or sharing with them. They are unaware of vendors building AI into products that have access to sensitive information and yet they continue deploying it. 

    This Is Not Science Fiction

    The threats described in Google’s report are not science fiction involving self-aware machines. It is much more practical and therefore far more dangerous.  

    For clients and MSPs alike, this means identity management, access controls, monitoring, and incident readiness are more critical than ever. The traditional assumption that we humans will catch and stop attacks before damage is done, is becoming less realistic by the day. 

    What Executives Should Do Now

    1. Require verbal verification for money movement: No changes to banking, payment, wire, or vendor account information without a phone call to a known contact.
    2. Inventory every AI system in the business: Know what AI tools employees and vendors are using, what data they access, and where sensitive information is flowing.
    3. Treat AI as an attack surface: Apply the same security controls to AI platforms, prompts, APIs, and data stores that you apply to other critical systems.
    4. Strengthen identity security: Prioritize MFA, conditional access, privileged access controls, and continuous monitoring. Identity is increasingly the primary target.
    5. Assume attacks will happen at machine speed: Review incident response plans and eliminate delays that require unnecessary human intervention.
    6. Train employees to distrust familiarity: Legitimate accounts, familiar voices, realistic websites, and accurate business context are no longer proof of legitimacy.
    7. Evaluate vendor AI risk: Ask vendors what AI features are enabled, what data is exposed, and how those systems are secured.
    8. Review all AI-generated code and automations: Don’t assume efficiency improvements equal security improvements. Every automation creates new opportunities for abuse.
    9. Implement rapid escalation procedures: Staff should know exactly who to call when something feels wrong, even if they cannot explain why.
    10. Promote a culture of healthy paranoia: Make it acceptable to verify, question, and challenge unusual requests. A five-minute phone call is often cheaper than a six-figure loss.

    Bottom Line

    The era of assuming humans will spot and stop attacks before damage occurs is ending. Know where your AI is, protect your identities, verify financial transactions out-of-band, and prepare your organization to respond at machine speed.