According to Bitsight TRACE’s 2025 State of the Underground report, the most exposed devices tied to critical vulnerabilities were found in the United States, and the most affected sectors included Information (telecom, IT) and Professional, Scientific, and Technical Services (including security and software vendors).
Even the most security-conscious industries are struggling to maintain visibility over exposed assets, especially those introduced by third parties. As of this blog’s publication, Bitsight threat research has identified over 230 million exposures in the U.S. alone, representing more than 40% of all exposures worldwide. That’s a staggering number, one that should stop any security leader in their tracks. How many of those 230 million exposures are you at risk for? Are your vendors at risk for? Are their vendors at risk?
In a recent study, Bitsight’s Dr. Ben Edwards predicted up to 59,000 new CVEs would be published in 2025. But with the NVD (NIST’s vulnerability database) still struggling to keep up, many of these vulnerabilities aren’t being fully analyzed thus creating a growing intelligence gap. As the volume of CVEs rises, the odds increase that a truly dangerous vulnerability slips through the cracks, especially on untracked, unmanaged, or vendor-owned assets. In other words, Shadow IT.
Without visibility into your full digital footprint, including assets you didn’t know existed, high-risk vulnerabilities can sit unpatched and exploited. You can only patch what you are aware of.
A simple analogy
Imagine your parents know every toy in your room. But one day, your friend brings a toy and hides it under your bed. That toy might be fun, it could also be sharp or dangerous and no one knows it’s there to check.
That’s what Shadow IT is like: unauthorized tech that’s introduced without oversight. And when it’s your vendors—or even their vendors—bringing it in, the risk becomes harder to control and nearly impossible to see.
What is third- and fourth-party shadow IT?
Shadow IT refers to devices, apps, cloud services, or infrastructure spun up without IT’s knowledge or approval. This includes:
- Marketing microsites hosted on your subdomains
- Dev or staging environments containing live data
- Public cloud buckets or SaaS portals using your brand
- DNS delegations managed by vendors
While third-party Shadow IT involves assets introduced by your immediate vendors, fourth-party Shadow IT refers to assets introduced by your vendors’ vendors—integrators, cloud hosts, subcontractors—often outside your direct line of sight. Those assets can still carry your domain, your logo, or your data.
These assets might not appear in any inventory, but they’re visible to attackers, indexable by search engines, and exploitable like any other exposed infrastructure.
Examples of shadow IT that could live on your network:
- Messaging apps used on corporate-owned devices (Snapchat, WhatsApp, Slack, Facebook Messenger, Signal, Skype)
- Physical devices not monitored by IT but connected to your network, including:
- Personal smartphones
- Laptops (we will hit on more later but this can include your family’s devices connected to your home internet while you’re working from home)
- Flash drives
- Cloud storage (Dropbox, Google Drive, AWS)
- Workplace efficiency apps meant to increase productivity (Trello, Airtable, Wrike, Monday.com, etc.)
- And more...
Why shadow IT happens
Shadow IT, (first, third, or fourth party), is usually not malicious. It’s driven by:
- The need to move fast
- Bypassing lengthy approval or onboarding processes
- Vendors building “quick fixes” or campaign infrastructure without oversight
But lack of visibility is lack of control. And when it comes to fourth-party risk, you may not even know the vendor exists, let alone what they’ve exposed on your behalf.
Real-world risks of Shadow IT
- Subdomain takeovers: If a vendor (or their vendor) forgets to decommission a hosted microsite, attackers can hijack it under your brand.
- Data exposure: Dev, staging, or storage environments can leak sensitive customer information.
- Malware hosting: Dormant vendor assets can be used to serve phishing or malware from trusted domains.
- Compliance failures: Regulatory bodies like GDPR, DORA, and NIS2 don’t differentiate between 1st-, 3rd-, or 4th-party when it comes to responsibility for exposed data.
Example:
A fintech firm hired a digital marketing vendor for a three-month campaign. That vendor outsourced hosting to another provider (a 4th party), spinning up a microsite under securepromo.finbrand.com. The campaign ended. The 4th-party host kept the site live (intentionally or unintentionally). Months later, it was quietly compromised and redirected users to a phishing site mimicking the fintech's login portal.
IT never knew the asset, or the 4th party, existed. But the brand and customer damage was real.
This is why it is important to monitor your company, your vendors, and your vendors’ vendors. The attack surface is vast, ensure you are protected.