TL;DR

Three major supply chain security incidents in June 2026 expose how attackers are pivoting from direct attacks to compromising the tools and vendors your business already trusts. ServiceNow's API flaw let attackers query customer data without authentication, a ClickFix campaign turned legitimate WordPress sites into malware delivery platforms targeting Australian infrastructure, and nation-state actors built covert networks of compromised devices to infiltrate organizations through their supply chains. If you are not actively auditing your vendor security posture this week, you are already behind.

The ServiceNow Breach: When Your SaaS Platform Opens the Door

ServiceNow, a platform used by over 8,000 enterprise customers including roughly 80% of Fortune 500 companies, disclosed a security incident in which attackers exploited an unauthenticated access flaw through a vulnerable API endpoint. The vulnerability allowed threat actors to query data directly from customer instances without needing valid credentials.

What happened: Attackers discovered and exploited an API endpoint that lacked proper authentication controls. Through this flaw, they could submit crafted queries to pull sensitive data from customer ServiceNow instances — including ticket details, employee information, internal processes, and potentially access credentials stored in knowledge base articles. The flaw was a textbook case of a broken access control vulnerability at the platform level.

How bad was it: The scope is significant because ServiceNow sits at the intersection of IT service management, HR workflows, and security operations for thousands of organizations. Any data stored in an affected instance — incident tickets, change management records, employee onboarding data — was potentially exposed. While ServiceNow has not publicly disclosed exact customer counts or financial impact, the average cost of a data breach in 2025 reached $4.88 million according to IBM's Cost of a Data Breach report, and platform-level breaches tend to compound that figure across multiple victims simultaneously.

How it could have been prevented: ServiceNow should have enforced stricter API authentication requirements, including mandatory token validation and rate limiting on query endpoints. On the customer side, businesses should have been limiting the types of data stored in shared platform instances and implementing their own monitoring for unusual API query patterns.

What to do this week: Audit every SaaS platform that holds sensitive business data. Demand that your vendors provide documentation of their API security testing, authentication enforcement policies, and incident response timelines. If a vendor cannot tell you how they test for unauthenticated access flaws, assume those flaws exist.

ClickFix and Vidar Stealer: When Trusted Websites Betray Your Users

The Australian Signals Directorate's Australian Cyber Security Centre (ASD ACSC) issued an advisory on a campaign using a social engineering technique called ClickFix to distribute Vidar Stealer through compromised WordPress websites, specifically targeting Australian infrastructure and organizations.

What happened: Threat actors compromised legitimate WordPress websites — sites that your employees might visit as part of normal business operations. These sites were then modified to display fake error messages or CAPTCHA prompts instructing visitors to "fix" a problem by copying and pasting a PowerShell command into their terminal. This is the ClickFix technique: it tricks users into executing malicious code themselves, bypassing many traditional security controls. The delivered payload was Vidar Stealer, a well-known information-stealing malware that harvests credentials, browser data, cryptocurrency wallets, and session tokens.

How bad was it: Vidar Stealer is particularly dangerous in a business context because it steals session cookies and saved browser credentials. An attacker with valid session tokens can bypass multi-factor authentication entirely. In previous campaigns, Vidar has been linked to secondary ransomware deployments. Organizations affected through compromised supply chain websites faced credential exposure, potential lateral movement, and the downstream cost of forced password resets, session revocations, and incident investigation — costs that easily reach tens of thousands of dollars per incident for mid-size businesses.

How it could have been prevented: Organizations should have been running web filtering and DNS-level blocking that identifies newly compromised sites. Endpoint detection and response (EDR) solutions tuned to flag PowerShell execution initiated from browser copy-paste actions would catch the ClickFix technique. User security awareness training specifically covering social engineering tactics that instruct users to run commands would reduce click-through rates.

What to do this week: Verify that your organization has web filtering active and that your EDR solution is configured to flag suspicious PowerShell execution. Run a quick awareness refresh with your team covering the ClickFix technique specifically — show them what the fake prompts look like. If any of your vendors or partners host WordPress sites that interact with your business, ask them what their patching and monitoring cadence looks like.

China-Nexus Covert Networks: Nation-State Supply Chain Infiltration

A joint advisory from the ASD ACSC and partner agencies outlined a significant shift in the tactics, techniques, and procedures used by China-nexus cyber actors to build covert networks of compromised devices, targeting organizations through their connected supply chains.

What happened: State-sponsored actors have been systematically compromising network devices — routers, VPN gateways, IoT sensors, and other infrastructure components — to build persistent covert networks. These compromised devices are then used as stepping stones to access the actual target organizations. The advisory highlights a shift toward exploiting supply chain relationships: instead of attacking a hardened target directly, actors compromise a less-defended vendor or partner in the target's supply chain and move laterally through trusted connections.

How bad was it: Nation-state supply chain compromises are among the most damaging incidents because they can persist undetected for months or years. The advisory indicates these actors are targeting critical infrastructure, government agencies, and large enterprises. The cost of discovering and remediating a nation-state-level compromise — including network rebuilds, credential resets across entire organizations, and regulatory reporting — can run into millions of dollars per victim. The broader economic impact of infrastructure disruption compounds this further.

How it could have been prevented: Network segmentation that limits what a compromised device can access. Zero-trust architecture that does not grant implicit trust based on network location. Regular firmware audits of all network-connected devices, especially those from smaller vendors who may not have robust security programs. Mandatory vulnerability disclosure and patching SLAs in vendor contracts.

What to do this week: Inventory every network device your business relies on — routers, switches, VPN appliances, IoT devices — and check each one against current vulnerability databases. Review which vendors have direct network connections to your environment and whether those connections are appropriately segmented. Add a clause to your vendor contracts requiring notification within 24 hours of any security incident that could affect your data.

The OpenClaw Warning: AI Agents Are the New Supply Chain Surface

In a finding that should alarm every business integrating AI tools, researchers demonstrated that the OpenClaw AI email agent fell for phishing attacks across multiple configuration profiles, leaking user data through tactics commonly used against human targets.

What happened: A phishing simulation targeting the OpenClaw AI agent showed that the tool was susceptible to standard social engineering techniques — deceptive links, spoofed sender addresses, and urgent language. The agent, designed to manage email on behalf of users, processed malicious messages and exposed user data that a human operator would likely have flagged as suspicious.

Why this matters for supply chain security: AI agents and copilots are rapidly being integrated into business workflows, often with broad access to email, documents, and internal systems. They represent a new class of supply chain risk: your vendor's AI agent now has access to your data, and if that agent can be phished, your data is exposed. As businesses rush to adopt AI-powered tools, the security of those tools themselves becomes a critical third-party risk factor.

What to do this week: Inventory every AI tool and agent that has access to your business data. For each one, determine what data it can access and what security testing the vendor has performed against social engineering and prompt injection attacks. If the vendor cannot demonstrate robust security testing, restrict the tool's access immediately.

FAQ

How do I assess which vendors pose the highest risk to my business? Rank your vendors by the sensitivity of data they can access and the directness of their network connection to your environment. A SaaS platform with access to HR data and a direct API integration is higher risk than a vendor who only receives encrypted file transfers. Focus your auditing efforts on the top 20% of vendors by data access.

What should I include in a vendor security questionnaire? At minimum, ask about: their most recent penetration test results and frequency of testing, their incident response plan and notification timelines, their employee security training program, their patching cadence for critical vulnerabilities, their use of multi-factor authentication internally, and whether they carry cybersecurity insurance. Ask for a SOC 2 Type II report if they handle sensitive data.

Is my business too small to be targeted through a supply chain attack? No. Supply chain attacks are opportunistic by nature. When attackers compromise a platform like ServiceNow, they are not selecting individual targets — they are grabbing data from every accessible instance. Small and mid-size businesses often have weaker security controls, making them easier secondary targets and attractive stepping stones to reach their larger partners or clients.

How often should I review my vendor security posture? At least annually for all vendors, and quarterly for any vendor with direct network access to your environment or access to regulated data (healthcare, financial, personally identifiable information). Any vendor that has experienced a public security incident should be reviewed immediately.

Conclusion

Supply chain attacks succeed because they exploit trust — trust in your SaaS platforms, trust in the websites your team visits, trust in your network equipment vendors, and now trust in the AI agents acting on your behalf. The incidents from just the past week demonstrate that this trust is being actively and systematically exploited by criminal and nation-state actors alike.

Your move is straightforward: stop assuming your vendors are secure and start verifying. This week, pick your three most critical third-party tools and demand security documentation. Inventory your internet-facing devices and check them against known vulnerabilities. Talk to your team about ClickFix-style social engineering. And if you have not mapped out every AI agent with access to your business data, do it now.

Visit consult.lil.business for a free cybersecurity assessment and find out where your supply chain vulnerabilities are before someone else does.

References

  1. ASD ACSC Advisory — ClickFix distributing Vidar Stealer via WordPress targeting Australian infrastructure
  2. ASD ACSC Advisory — Defending against China-nexus covert networks of compromised devices
  3. ServiceNow discloses security incident exposing customer data — BleepingComputer
  4. NIST SP 800-161 Rev. 1 — Cybersecurity Supply Chain Risk Management Practices for Systems and Organizations

TL;DR

  • A company called Marquis Software Solutions helps over 700 banks with marketing and data — and hackers broke into Marquis, not the banks themselves. But because Marquis had bank customer data, over 800,000 people got their personal info exposed [1][3].
  • The hackers got in through a known security flaw in a firewall product that had a fix available — like leaving a broken lock on the front door even though a new lock was ready to install [6].
  • It took four months for anyone to tell the affected people what happened [1].
  • The fix-up work Marquis did afterward — installing monitoring tools, changing passwords, rebuilding systems — is stuff that should've been there from the start [1][8].

What Happened? Think of It Like a Neighborhood

Imagine your bank is a house with good locks and cameras. But you hire a lawn-mowing company and give them a spare key to the backyard shed — the one with important paperwork inside.

Marquis Software Solutions is that lawn-mowing company. This Plano, Texas firm helps over 700 banks with advertising and data work. Banks gave Marquis access to customer names, Social Security numbers, addresses, birthdates, and bank account details [1].

On August 14, 2025, hackers didn't break into any bank. They broke into Marquis — the company with spare keys to 700+ sheds. One break-in, 80+ banks affected, over 800,000 people exposed [1][3].

How Did the Hackers Get In?

Marquis used a firewall (like a front gate) made by SonicWall. That gate had a known broken latch — security experts rated it 9.3 out of 10 for danger, and a fix was available [6]. But Marquis never installed it. Hackers — possibly a group called Akira — walked right through [4][7].

SonicWall products have appeared on the government's "known broken locks" list 14 times. Eight of those were used in ransomware attacks, where hackers lock your files and demand money [4].

Why Did It Take So Long to Tell People?

The break-in was in August 2025. People weren't told until December — four months later [1][3]. That's four months of stolen Social Security numbers floating around while victims had no idea. IBM's research shows breaches already take an average of 277 days to contain, and adding silence makes it worse [8].

What Should You Do?

  1. Check the mail for breach notification letters from your bank.
  2. Freeze credit reports at Equifax, Experian, and TransUnion — it's free and stops anyone from opening fake accounts in your name.
  3. Watch bank statements for transactions that don't belong.
  4. Use strong, unique passwords — a password manager helps.
  5. Turn on two-factor authentication — that extra code when you log in adds a second lock to the door.

FAQ

A third-party data breach is when hackers don't attack your company directly — they attack a company your company works with. In this case, hackers attacked Marquis Software Solutions, which had access to bank customer data. The banks themselves weren't hacked, but their customers' data was still stolen because it was stored at Marquis [1].

The stolen data includes people's full names, Social Security numbers, home addresses, phone numbers, dates of birth, and bank account information. This is enough for criminals to try to steal someone's identity or open fake accounts [1][3].

The Maine Attorney General filing lists 672,075 people. Across all state filings, the number is over 823,000. The real total could be as high as 1.35 million people across 74 to 80+ banks and credit unions [1][3].

Yes — this appears to be a ransomware attack, where hackers lock up data and demand payment. Reports suggest Marquis may have paid the ransom, based on a filing by Community 1st Credit Union that was later deleted [1].

Freeze your credit at Equifax, Experian, and TransUnion — it's free and it stops strangers from opening accounts in your name. Monitor your bank accounts for unfamiliar activity. Use unique passwords and turn on two-factor authentication wherever you can. These steps won't undo a breach, but they make stolen data much harder to use against you [8].


Whether you run a small business or manage IT for a larger organization, understanding who has access to your data — and how they protect it — is one of the most important things you can do.

Talk to lil.business about vendor risk →


References

[1] H. Kanapi, "US Banks Hit by Massive Third-Party Data Breach," The Daily Hodl, Mar. 21, 2026. [Online]. Available: https://dailyhodl.com/2026/03/21/us-banks-hit-by-massive-third-party-data-breach-sensitive-information-of-672075-people-potentially-exposed/

[3] Maine Attorney General, "Data Breach Notifications," 2026. [Online]. Available: https://www.maine.gov/agviewer/content/ag/985235c7-cb95-4be2-8792-a1252b4f8318/data-breach-notifications.html

[4] CISA, "Known Exploited Vulnerabilities Catalog," 2026. [Online]. Available: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

[6] NIST, "NVD - CVE-2024-40766," 2024. [Online]. Available: https://nvd.nist.gov/vuln/detail/CVE-2024-40766

[7] Arctic Wolf Labs, "SonicWall VPN Credential Theft Analysis," 2025. [Online]. Available: https://arcticwolf.com/resources/blog/

[8] IBM Security, "Cost of a Data Breach Report 2025," IBM, 2025. [Online]. Available: https://www.ibm.com/reports/data-breach