1. A Typical Monday Morning in 2026

A 14-person personal injury law firm opens for business at 9 AM. The paralegal tries to access the client database. Permission denied. She calls IT β€” which is actually just the office manager who handles the router. He can't log in either. The file server is showing a ransom note: a .txt file named READ_ME_NOW.txt, demanding $95,000 in Bitcoin within 72 hours or client files go public. Three years of case documents, settlement records, and medical histories. Gone.

This is not a hypothetical. INC Ransom group alone claimed 20+ law firms in the first four months of 2026. Personal injury firms were specifically targeted in a 2026 campaign documented by Halcyon, which tracked 200+ ransomware incidents against legal services organizations between 2025 and early 2026. The reason law firms are targeted isn't random β€” it's the combination of sensitive data, regulatory pressure to resolve incidents fast, and the understanding that protecting attorney-client privilege often matters more to a firm than the actual ransom amount.

Dental practices, accounting firms, and logistics companies are in the same category. Healthcare saw 636 ransomware attacks in 2025 alone, with smaller providers accounting for 26% of those incidents. A patient management system locked down by ransomware in a 2026 incident had an owner who said something that's become almost clichΓ© in incident reports: "I thought we were too small for hackers to notice."

"We had a backup. We thought we were fine. What we didn't know was that the attackers had been inside our network for nine days before the encryption ran. By that point, they had already exfiltrated our client list, found our backup server, and deleted it. The backup we were counting on didn't exist anymore."

2. Who Gets Hit: The Target Distribution

The shift toward SMB targeting has been building since 2022 but accelerated sharply after law enforcement operations disrupted several large ransomware groups in 2024. The groups that survived and the new ones that emerged focused heavily on volume β€” targeting dozens of smaller organizations instead of spending months infiltrating one enterprise.

Ransomware attacks by target organization size β€” 2025 data
<50 employees
42%
50–250 employees
29%
250–500 employees
14%
500–1,000 employees
8%
1,000+ employees
7%
Source: Verizon DBIR 2025, Huntress Ransomware Statistics 2026. Percentages rounded.

The 42% figure for businesses under 50 employees is striking. This is the category that includes your accountant, your dentist, a three-location restaurant chain, a regional logistics broker. Organizations that almost certainly don't have a full-time IT person, let alone a security team.

What's changed in 2026 is the scale of automation. Attackers use scanning tools to continuously probe the internet for vulnerable systems across millions of IP addresses simultaneously. When a scan hits an exposed service β€” an old VPN endpoint, a misconfigured remote desktop, an unpatched CMS β€” it flags it automatically. A human attacker then picks up the lead and initiates targeted intrusion. The economics only work because the initial scanning costs essentially nothing. Your company's exposure becomes a discovered lead before anyone from the outside has even looked at your company specifically.

3. The Groups Behind the Attacks

The ransomware landscape in 2026 is more fragmented than it was in 2023. The major operations β€” LockBit, ALPHV/BlackCat β€” were disrupted by law enforcement, but they either reconstituted or spawned successor groups. Here are the four groups most actively targeting smaller organizations right now:

Qilin
Most Active Q1 2026
41%
of all Q1 2026 victims, with Akira, LockBit & The Gentlemen
Preferred targets: Healthcare, education, legal services, regional manufacturing. Qilin alone outpaced the bottom 50 ransomware groups combined in Q1 2026 victim count.
Cl0p
Mass Exploitation
22
attacks in a single day (Feb 1, 2026)
Method: Mass exploitation of enterprise software vulnerabilities (CVE-2025-61882 and others). Hits healthcare, finance, logistics, and technology across multiple countries simultaneously.
LockBit
Persistent
5.0
version currently active (post-law enforcement disruption)
Preferred targets: SMBs without IT staff, specifically via unpatched VPN gateways, RDP exposure, and phishing. Uses SMB protocol for internal spreading once inside.
INC Ransom
Sector-Focused
20+
law firms claimed in first 4 months of 2026
Preferred targets: Legal services, medical practices, accounting firms. Prioritizes organizations where client confidentiality creates maximum leverage for extortion.

What these groups share is a Ransomware-as-a-Service (RaaS) model. The core developers build and maintain the malware. Affiliates β€” essentially independent contractors β€” carry out the attacks and split the ransom revenue, typically 70/30 or 80/20 in favor of the affiliate. This model explains why the volume of attacks can scale so rapidly: you don't need more developers, you need more affiliates, and affiliates are attracted to easy targets. SMBs are easy targets.

4. The Three Gaps That Make SMBs Vulnerable

If you ask a ransomware affiliate why they targeted a particular company, the honest answer would rarely be "because they had interesting data." It's almost always a variant of: "because getting in was easy." The three conditions that create "easy" keep appearing across incident reports.

Gap 1: No one is watching at 2 AM

Enterprise security operations centers run 24/7. When a threat detection system fires an alert at 2:14 AM β€” unusual SMB connections between hosts that don't normally talk, a new administrative account created outside business hours, 40GB of outbound traffic to an unknown IP β€” someone responds. In one documented 2026 incident, an 800-location retail chain detected and contained a ransomware attack in 1 hour and 47 minutes because an automated system triggered an alert and a human picked it up immediately.

Most SMBs have no equivalent. The person who would investigate an anomaly is asleep. If the company has a logging system at all, the logs accumulate unreviewed. Attackers know this rhythmically β€” they frequently trigger final payloads between 1 AM and 4 AM on weekday mornings, after spending days or weeks being methodical during business hours.

Gap 2: Unknown attack surface

Enterprise security teams maintain asset inventories. They know every public-facing system, every IP range, every exposed service. They run scheduled vulnerability scans and get weekly reports on what's changed.

Most SMBs don't know what's exposed. Not because they're negligent β€” because nobody told them this was something they needed to know. A remote desktop endpoint left open after a COVID-era work-from-home setup. A subdomain running an old WordPress install that nobody maintains. An S3 bucket set to public during a developer test three years ago and never locked down. API keys in a JavaScript file that's been cached by Shodan. These are real attack entry points that companies discover not through proactive scanning, but during post-incident forensics β€” after the damage is done.

Gap 3: The double extortion problem

The old model was: encrypt everything, demand ransom, restore backups if you don't pay. Most reasonable organizations responded to this by maintaining good backups. So attackers added a second layer: steal first, encrypt second. Now even if you restore from backup within hours, the attacker still has your client data, your financial records, your employee files. They'll publish it unless you pay. Backup discipline no longer neutralizes the threat β€” it only removes one dimension of it.

5. The 5-Day Attack Window

The median time from initial compromise to ransomware execution dropped from 14 days (2023) to just 5 days in 2025. Attackers have sped up. They've automated more of the internal reconnaissance. The window to catch them before they detonate is narrowing fast.

Here's what those five days typically look like:

0
Day 0 β€” Initial access

The attacker gets in. You don't notice.

Entry is typically via one of four routes: a phishing email that captures credentials, an exploited vulnerability on a public-facing service, a compromised VPN credential purchased on a dark web marketplace, or brute-forced RDP. At this stage nothing is encrypted or deleted. The foothold is silent.

  • Most common entry: phishing (33%), exploited public service (28%), stolen credentials (24%)
  • Phishing emails increasingly bypass standard filters using QR codes or legitimate file hosting
1
Days 1–2 β€” Reconnaissance

Mapping your network. Finding the crown jewels.

The attacker uses native Windows tools β€” PowerShell, WMI, net commands β€” to avoid triggering antivirus. They map which machines exist, which accounts have admin rights, where the file server is, whether backups are network-accessible. BloodHound is commonly used to automatically map Active Directory privilege paths. This phase looks like normal admin traffic unless someone is specifically looking for it.

2
Days 2–4 β€” Privilege escalation & data exfiltration

They go admin. Then they take everything before breaking it.

Domain administrator access is achieved, usually by exploiting a vulnerability or harvesting a privileged credential. Once at this level, the attacker accesses backup systems and either deletes them or disconnects them from the network. Sensitive data β€” client lists, financial records, HR files β€” is uploaded to an attacker-controlled server. This is the step that makes backup restoration insufficient as a solo defense.

3
Day 4–5 β€” Encryption & ransom note

2 AM. Everything stops.

The ransomware payload deploys across every accessible system simultaneously β€” workstations, file servers, cloud-synced drives. Encryption typically takes 30 minutes to a few hours depending on data volume. The ransom note appears. This is the first visible sign that something happened β€” but the real damage (data theft, backup deletion) was done days ago. Paying the ransom at this point only gets you a decryption key, not your data back from their servers.

Alert

The implication most organizations miss: By the time you see the ransom note, you're negotiating. The moment to act was during days 1–4, when the attacker was visible only as anomalous network behavior β€” if anyone had been looking. This is why prevention and detection matter more than response plans for most SMBs.

6. What a Ransomware Attack Actually Costs

Media coverage focuses on ransom amounts. The actual cost is almost always larger than the ransom, and often larger than the organization expects. Here's where the money goes:

$120K–$1.24M
Total cost range per SMB ransomware incident (excluding ransom) Β· Source: Verizon, Mastercard SMB Survey 2025
Incident Response
$20K–$80K
Forensic investigators, IR retainer activation, evidence preservation. Billed by the hour. Complex cases run 2–6 weeks.
System Rebuild
$15K–$60K
Rebuilding compromised systems from scratch. Cannot simply restore infected systems β€” everything must be verified clean.
Business Interruption
24-day avg downtime
Revenue loss during outage. For a $500K/year firm, 24 days β‰ˆ $33K. Client losses during disruption often exceed this.
Legal & Regulatory
$10K–$150K+
Breach notification, regulatory counsel, GDPR/APPI compliance response. Class action exposure if client data was leaked.
Client Losses
Highly variable
Clients lost due to breach notification rarely return. For service businesses, this is often the largest long-term cost.
Post-Incident Security
$15K–$80K/year
Insurance premium increases (often 2–5Γ—) and mandatory security improvements required for renewal.

The Mastercard survey finding that 1 in 5 SMBs that suffer a cyberattack go bankrupt or close isn't dramatic language β€” it tracks with the cost structure above. For a 20-person professional services firm billing $1.5M/year, a $350,000 total incident cost plus 30% client attrition is genuinely existential.

7. Twelve Exposure Points Most SMBs Can't See

The following are not theoretical vulnerabilities. These are the specific conditions that appear most frequently in SMB breach incident reports β€” the entry points that attackers find before the company does, because attackers run automated scans continuously and most companies scan never.

Common SMB attack surface exposures β€” check how many apply to you

RDP (port 3389) exposed to the internet Remote desktop directly accessible without VPN. One of the most common ransomware entry points. Brute-forced or used with purchased credentials. ⚠ High risk · Found in majority of SMB ransomware cases
Outdated or unpatched public-facing software CMS (WordPress, Drupal), VPN appliances, email servers with known CVEs. Cl0p specifically scanned for CVE-2025-61882 across millions of IPs. ⚠ High risk · Automated mass-exploitation in progress
SPF/DKIM/DMARC missing or misconfigured Without these DNS records, your domain can be spoofed for phishing. Attackers send emails "from you" to your clients or employees. ⚠ High risk · Enables phishing and BEC attacks
API keys or secrets in public JavaScript files Cloud credentials, payment processor keys, and database tokens in frontend code are indexed by Shodan and Censys. Regularly rotated but often forgotten. ⚠ High risk · Directly grants cloud access
Subdomains pointing to decommissioned services DNS records for services that no longer exist can be hijacked. A subdomain takeover lets attackers serve malicious content under your domain. ⚠ Medium–high risk Β· Often invisible without DNS scanning
Credentials in data breach databases Employee email and password combinations from past third-party breaches. Used for credential stuffing against your VPN, email, and admin portals. ⚠ High risk · Often the source of "first access"
SSL certificate expiry or weak cipher configuration Expired certificates break trust warnings but also signal poor maintenance. Weak TLS configurations enable man-in-the-middle interception. ⚠ Medium risk
Cloud storage (S3, GCS) set to public Buckets created for temporary use and never locked down. Often contain customer data, internal documents, or backup archives. ⚠ High risk · Direct data exposure
Server version and tech stack fingerprinting HTTP headers often reveal exact software versions and frameworks. Attackers use this to match against known vulnerability databases before initiating attacks. ⚠ Medium risk · Reduces attacker effort significantly
Backup servers accessible from the network Network-attached backups that can be reached from the same network as workstations are discovered and deleted before ransomware deploys. ⚠ Critical · Eliminates your primary recovery option
CORS misconfiguration on APIs APIs that accept requests from any origin enable cross-site attacks and unauthorized data access. Common in rapidly built applications. ⚠ Medium risk
Error messages exposing internal file paths or stack traces Detailed error pages reveal technology stack, database structure, and internal paths. Useful reconnaissance for targeted attacks. ⚠ Medium risk · Significantly aids attacker reconnaissance

How many of the above can you answer with confidence right now? If the honest answer is "I don't know" for more than two or three of them, you have an attack surface that's essentially unmapped β€” which is exactly the condition attackers scan for at scale.

8. The Honest Takeaway

Here's what security vendors rarely say plainly: you cannot make your organization completely unattackable. The threat landscape is too dynamic, the attack surface too broad, and the resources available to a 20-person company too limited to achieve perfect security.

What you can achieve β€” and what actually shifts the equation β€” is making your organization a significantly harder target than average. Attackers operate on economics. When they scan a block of IP ranges and your exposed services come back clean, your SSL grades good, your email authentication intact, and your credentials absent from breach databases, they move to the next target. Most SMBs are not being targeted because someone specifically wants their data. They're being targeted because a scan found an open door.

Key Question

The question worth asking: If an attacker ran a reconnaissance scan against your company's domain right now β€” the same scan that Shodan, Censys, and every serious threat actor runs continuously β€” what would they find? If you don't know the answer to that, you don't know your risk. And neither does your insurer, your clients, or your board.

Regular external scanning β€” running those scans against yourself before anyone else does β€” is the baseline capability that closes the information asymmetry. It's not a guarantee. It's the difference between knowing your exposure and not knowing. That distinction, at the moment a criminal is deciding which company on a list is worth pursuing, is frequently the one that matters.

Sources & References

  1. Verizon Data Breach Investigations Report 2025 β€” SMB breach statistics, ransomware prevalence (44% of confirmed breaches)
  2. Huntress, "Ransomware Statistics 2026: Attack Trends & Business Impact" β€” target distribution by organization size
  3. Mastercard SMB Cybersecurity Survey 2025 (5,000+ SMB owners) β€” 1 in 5 SMBs that suffer an attack go bankrupt or close
  4. Industrial Cyber, "Ransomware sector reconsolidating as Qilin, LockBit, and The Gentlemen expand influence in Q1 2026" β€” Q1 2026 victim attribution
  5. Ransom-DB, "Cl0p Ransomware Group Analysis 2026" β€” 22 attacks on February 1, 2026; CVE-2025-61882 exploitation
  6. Halcyon, "INC Ransom Group Mounts Rapid Campaign Against Law Firms" β€” 200+ legal sector ransomware incidents tracked 2025–2026
  7. Comparitech, "Healthcare ransomware roundup Q1 2026" β€” 636 healthcare ransomware attacks in 2025
  8. Sophos, "State of Ransomware 2025" β€” median intrusion-to-execution time of 5 days; $120K average SMB recovery cost
  9. Group-IB, "High-Tech Crime Trends Report 2026" β€” supply chain attack group identification
  10. SecurityToday.de, "Major Retail Chain Halts Ransomware Attack in Under 2 Hours" (Jan 2026) β€” 1h47m containment case study

Find Out What an Attacker Would See

10 questions. Instant results. No signup required. Get a baseline read on your organization's security posture before someone else does.

Questions? Email info@avisail.com Β· Response within 1 business day