
In early 2026, Nike disclosed a ransomware incident. Attackers encrypted some systems. Nike restored from backups. Operations continued with minimal disruption.
Sounds like a contained incident, right?
Here's what Nike didn't emphasize in their public statements:
Before encrypting anything, the attackers exfiltrated approximately 1.4 terabytes of intellectual property:
- Unreleased shoe designs and prototypes
- Manufacturing processes and specifications
- Supplier contracts and pricing agreements
- Patent applications in development
- Marketing strategies and launch plans
- R&D investment roadmaps
The ransomware encryption was theater. The real attack was industrial espionage.
Nike could restore encrypted files from backups in hours. But they can't un-steal intellectual property that's already been copied. Those shoe designs planned for 2027 release? Competitors could have them now. Those supplier contracts with negotiated pricing? Publicly exposed or sold to rivals.
The ransom demand wasn't "pay us to decrypt your files." It was "pay us not to sell your trade secrets to your competitors."
After founding a CIAM platform that handled sensitive business data for thousands of companies, I learned that the real value isn't in the systems you encrypt—it's in the data you steal before anyone notices.
Traditional ransomware asked: "How much is system uptime worth to you?"
Modern ransomware asks: "How much are your trade secrets worth to your competitors?"
Let me show you why Nike's attack represents the evolution of ransomware from nuisance to existential business threat, and what it means for any company with intellectual property worth stealing.
What Actually Happened: The Attack Timeline
Nike hasn't disclosed full technical details, but the attack pattern matches what we're seeing across enterprise ransomware incidents in 2026.
Phase 1: Initial Access (Weeks to Months Before Detection)
Entry vectors for enterprise ransomware:
Phishing:
- Targeted emails to employees with system access
- Credential harvesting for VPN or email accounts
- Malicious attachments with embedded malware
Vendor compromise:
- Third-party with access to Nike systems
- Compromised vendor credentials used for lateral movement
- Supply chain attack through integrated systems
Vulnerability exploitation:
- Unpatched systems (VPNs, firewalls, web applications)
- Zero-day exploits purchased from underground markets
- Known vulnerabilities in legacy systems
The timeline: Attackers typically gain access weeks or months before the visible ransomware deployment.
Why the delay?
- Map the network architecture
- Identify valuable data stores
- Locate backup systems (to destroy before encryption)
- Establish persistence (multiple access methods)
- Exfiltrate data slowly (avoid detection)
By the time Nike detected the ransomware, attackers had already spent weeks inside the network.
Phase 2: Reconnaissance and Lateral Movement
What attackers did inside Nike's network:
Mapped intellectual property locations:
- Design systems (CAD files, 3D models, prototypes)
- Engineering databases (specifications, materials, processes)
- Legal systems (patents, trademarks, contracts)
- Marketing systems (campaigns, launch plans, budgets)
- Supply chain systems (supplier contracts, pricing, logistics)
Escalated privileges:
- Compromised admin accounts
- Exploited misconfigurations
- Leveraged weak password policies
- Bypassed segmentation controls
Established persistence:
- Created backdoor accounts
- Installed remote access tools
- Deployed command-and-control infrastructure
- Ensured multiple reentry methods
The goal: Find the most valuable data and ensure sustained access even if initial entry point is discovered.
Phase 3: Data Exfiltration (The Real Attack)
1.4 terabytes of data extracted before encryption:
What 1.4TB represents:
- Millions of documents
- Thousands of design files
- Hundreds of databases
- Years of R&D investment
- Billions in potential competitive advantage
How data was exfiltrated:
Slow and steady approach:
- Small data transfers over weeks (avoid bandwidth alerts)
- Encrypted channels to attacker infrastructure
- Disguised as legitimate traffic
- During off-hours when less monitored
Common exfiltration methods:
- Direct upload to attacker cloud storage
- Encrypted tunnels through compromised systems
- Staged exfiltration through multiple hops
- Disguised within normal network traffic
The key insight: By the time ransomware deployed, all valuable data was already stolen.
Phase 4: Backup Sabotage
Modern ransomware groups know companies have backups.
What attackers did before deploying encryption:
Identified backup systems:
- On-premises backup servers
- Cloud backup repositories
- Offline/air-gapped backups
- Snapshot and replication systems
Destroyed or encrypted backups:
- Deleted recent backup copies
- Encrypted backup repositories
- Corrupted backup databases
- Disabled backup automation
Why this matters:
- Restoring from backups becomes impossible or partial
- Increases pressure to pay ransom
- Extends recovery timeline from hours to weeks
Nike likely had offline backups (hence relatively quick recovery), but many companies don't.
Phase 5: Ransomware Deployment
The visible attack:
- Mass encryption of file servers and databases
- Ransom notes deployed across systems
- Operations disrupted
- Public disclosure required
But this was just leverage for the real extortion:
The dual ransom demand:
- "Pay $X to decrypt your files" (which Nike could restore from backups)
- "Pay $Y to prevent us from selling your 1.4TB of IP to competitors" (which Nike couldn't prevent)
The second demand is what made this attack devastating.
When building the CIAM platform, we faced ransomware attempts. We had backups, so encryption wasn't catastrophic.
But if attackers had exfiltrated our customer database or authentication architecture, backups wouldn't help. The data would already be gone.
That's the shift: ransomware evolved from "pay to restore access" to "pay to prevent data exposure."
Why Trade Secrets Are the New Target
Traditional ransomware focused on system availability. Modern ransomware focuses on data value.
Here's why trade secrets are more valuable than encrypted systems:
They Can't Be Restored From Backups
System encryption:
- Restore from backups → problem solved
- Rebuild servers → inconvenient but manageable
- Recovery time: Hours to days
Data exfiltration:
- Can't "restore" stolen data
- Can't undo competitor knowledge
- Can't reclaim trade secret status once exposed
- Impact: Permanent
Nike's situation:
- Encrypted files restored quickly ✅
- Stolen IP? Still stolen ❌
They Have Competitor Value
Traditional ransom: "Pay or you can't access your files" Modern ransom: "Pay or we sell to your competitors"
For Nike specifically:
Unreleased shoe designs:
- Development cost: Millions per product line
- Market value: Billions in future sales
- Competitor value: Priceless (skip R&D, copy designs)
Manufacturing processes:
- Proprietary techniques developed over decades
- Cost savings: Pennies per unit × millions of units = millions annually
- Competitive advantage: Better margins than rivals
Supplier contracts:
- Negotiated pricing (revealing cost structures)
- Exclusive agreements (showing vulnerabilities)
- Volume commitments (business intelligence)
Attackers can:
- Sell to competitors directly (highest price)
- Leak publicly (destroy competitive advantage)
- Auction to multiple bidders (maximize revenue)
The leverage is permanent. Even if Nike pays, they can't verify data deletion.
They Create Multi-Year Damage
System downtime: Measured in hours or days
IP theft: Measured in years
Nike's timeline:
2026 (Attack year):
- Designs for 2027 products stolen
- R&D roadmap exposed
- Supplier pricing revealed
2027-2028:
- Competitors launch similar designs
- Market share erodes
- Pricing power diminishes
2029-2030:
- Technology advantage lost
- R&D investment wasted
- Competitive position weakened
The attack's impact extends far beyond the incident response period.
They're Protected By Law (But Only If Secret)
Trade secrets have legal protection under:
- Economic Espionage Act (U.S.)
- Defend Trade Secrets Act (U.S.)
- EU Trade Secrets Directive
- Various international agreements
But protection requires:
- Information derives value from secrecy
- Owner takes reasonable steps to maintain secrecy
- Information not generally known
Once stolen and disclosed:
- Trade secret status lost
- Legal protection gone
- Competitive advantage evaporates
Nike's stolen IP:
- Before theft: Protected trade secrets
- After public disclosure: Public information
- Recovery: Impossible
When building the CIAM platform, we treated our authentication architecture as trade secrets. We documented it internally but never publicly disclosed implementation details.
If ransomware had stolen and leaked our architecture, competitors could have replicated our approach without R&D investment.
That's why modern ransomware targets IP: it's the most valuable and least recoverable asset in your network.
The Double Extortion Business Model
Nike's attack exemplifies "double extortion"—a ransomware evolution that's become standard in 2026.
Traditional Ransomware (2015-2020)
Single extortion model:
- Encrypt victim's files
- Demand ransom for decryption key
- Victim pays or restores from backups
Victim's calculation:
- Cost of downtime vs. ransom amount
- Many chose backups over payment
Attacker's problem:
- Backups reduced payment rates
- Organizations got better at recovery
- Revenue per attack declined
Success rate: ~30% payment rate
Double Extortion (2020-Present)
Enhanced model:
- Exfiltrate valuable data (weeks before encryption)
- Encrypt systems (create immediate pressure)
- Demand payment for both decryption AND data non-disclosure
- Threaten public leak or competitor sale if unpaid
Victim's calculation changed:
- Backups solve encryption (old problem)
- Can't solve data theft (new problem)
- Payment becomes more attractive
Attacker's advantage:
- Two leverage points instead of one
- Data theft threat persists even after system recovery
- Higher payment rates
Success rate: ~50-70% payment rate
Nike's Specific Scenario
What Nike faced:
Threat 1: System encryption
- Nike's response: Restore from backups ✅
- Impact: Minimal, operations continued
- Ransom pressure: Low
Threat 2: IP disclosure
- Nike's response: ??? (no technical solution)
- Impact: Potentially catastrophic
- Ransom pressure: Extreme
The extortion demands:
- "Pay $X million to decrypt files" → Nike ignored (had backups)
- "Pay $Y million to prevent IP sale" → This is the real threat
Nike's dilemma:
- Pay ransom (funds criminals, no guarantee of data deletion)
- Don't pay (risk trade secrets on dark web or sold to competitors)
- Disclose publicly (required by regulations, alerts competitors)
There's no good option.
Why This Model Works
From attacker's perspective:
Data exfiltration advantages:
- Happens before detection (silent theft)
- Can't be "restored" (permanent leverage)
- Multiple monetization paths (ransom, dark web, competitors)
- Compounds damage (encryption + exposure)
Victim organization analysis:
Cost-benefit of paying:
- Ransom: $5-10 million (typical for Fortune 500)
- IP value: Billions in competitive advantage
- Brand damage: Incalculable if exposed
- Calculation: Paying seems "cheaper"
Cost-benefit of not paying:
- Recovery cost: Manageable (have backups)
- IP exposure risk: Catastrophic
- Competitor advantage: Years of lost market share
- Calculation: Not paying seems "expensive"
Attackers designed this calculus intentionally.
When building the CIAM platform, we evaluated ransomware insurance. The policies increasingly excluded data exfiltration coverage because insurers know organizations will pay to protect IP.
This creates a self-perpetuating cycle: high payment rates → more attacks → higher ransoms → more pressure to pay.
What Made Nike Vulnerable
Nike is a sophisticated, well-resourced company with security teams and tools. How did this happen?
The Intellectual Property Challenge
Nike's IP is distributed across systems:
Design and engineering:
- CAD systems (shoe designs, 3D models)
- PLM (Product Lifecycle Management) platforms
- Engineering databases (materials, specifications)
Business intelligence:
- ERP systems (supply chain, pricing, costs)
- CRM systems (customer data, sales strategies)
- Financial systems (margins, forecasts, investments)
Legal and compliance:
- Patent databases (applications in development)
- Contract management (supplier agreements)
- Trademark systems (brand protection)
Marketing and strategy:
- Campaign planning systems
- Launch calendars
- Market research databases
The problem: IP isn't in one location. It's everywhere.
Securing it requires:
- Data classification (what's confidential vs. public)
- Access controls (who needs each dataset)
- Encryption (at rest and in transit)
- Monitoring (detecting unusual access patterns)
- DLP (Data Loss Prevention) tools
The reality: Most companies have fragmented approaches to IP protection.
The Vendor and Integration Problem
Nike doesn't operate in isolation. Hundreds of vendors have system access:
Design partners:
- Agencies with access to marketing materials
- Manufacturers with product specifications
- Technology vendors with CAD system access
Business systems:
- Cloud providers hosting databases
- SaaS vendors with CRM/ERP data
- Analytics platforms with business intelligence
IT and security:
- Managed service providers
- Security vendors with network access
- Backup services with data copies
Each vendor is a potential entry point.
The challenge:
- Can't eliminate vendor access (business requires it)
- Can't monitor all vendor activity (too many integrations)
- Can't verify vendor security posture continuously
Attackers know this. They target the weakest vendor, not the strongest (Nike's) security.
The Insider Threat Gap
Ransomware groups increasingly use:
- Compromised employee credentials
- Social engineering of staff
- Malicious insiders (recruited or coerced)
Why this works:
Legitimate access:
- Employee credentials bypass security controls
- Normal user activity doesn't trigger alerts
- Access to valuable data is expected
Privilege escalation:
- Employees often over-privileged
- Lateral movement easier from inside
- Trust relationships between systems
When building the CIAM platform, we implemented zero-trust architecture:
- No implicit trust (even for employees)
- Continuous verification
- Least-privilege access
- Microsegmentation
Most companies still use perimeter security: Once you're inside (or have credentials), you can access most systems.
That's what ransomware groups exploit.
The Detection Time Problem
Industry average time to detect breach: 207 days (IBM 2024 report)
Nike's likely timeline:
- Attackers inside: Weeks to months
- Data exfiltration: Ongoing during that period
- Detection: Only when ransomware deployed
Why detection is slow:
Normal behavior patterns:
- Attackers use stolen credentials (looks legitimate)
- Data access within job role (doesn't trigger alerts)
- Exfiltration disguised as backup/sync (normal traffic)
Alert fatigue:
- Security teams overwhelmed with false positives
- Real threats buried in noise
- Critical alerts missed
Insufficient monitoring:
- Not all systems logged
- Logs not analyzed in real-time
- Behavioral analytics not deployed
By the time Nike detected the ransomware, 1.4TB was already gone.
The Competitive Intelligence Threat
Nike's stolen IP isn't just valuable to ransomware groups. It's intelligence gold for competitors.
What Competitors Could Learn
From unreleased designs:
- Upcoming product strategies
- Technology innovations
- Materials research
- Market positioning
From supplier contracts:
- Manufacturing costs (revealing margins)
- Volume commitments (showing market confidence)
- Exclusive agreements (identifying dependencies)
- Pricing negotiations (understanding leverage)
From R&D roadmaps:
- Future investment areas
- Technology bets
- Market expansion plans
- Innovation timelines
From marketing plans:
- Launch strategies
- Target demographics
- Pricing strategies
- Campaign budgets
The competitive value:
- Skip R&D costs (copy innovations)
- Undercut pricing (know Nike's costs)
- Pre-empt launches (beat to market)
- Poach suppliers (offer better terms)
The Corporate Espionage Market
Stolen corporate IP has multiple buyers:
Direct competitors:
- Willing to pay premium for rival's secrets
- Can claim "independent development"
- Difficult to prove espionage vs. parallel innovation
Nation-state actors:
- Industrial policy objectives
- Supporting domestic companies
- Economic advantage
Investment firms:
- Market intelligence for trading
- M&A advantage
- Competitive analysis
The dark web market for corporate IP is thriving.
Pricing examples:
- Fortune 500 trade secrets: $500K-$5M
- Patent applications: $100K-$500K
- Supplier contracts: $50K-$200K
- Product roadmaps: $200K-$1M
Nike's 1.4TB could be worth $10-50 million on this market.
Even if Nike pays the ransom, there's no guarantee attackers won't sell data anyway.
What Actually Needs to Change
Nike's incident isn't solved by better backup systems. It requires fundamental rethinking of how companies protect intellectual property.
1. Data-Centric Security (Not System-Centric)
Current approach: Protect systems and networks
Better approach: Protect data regardless of where it lives
Implementation:
Data classification:
- Identify trade secrets and critical IP
- Label by sensitivity level
- Tag with handling requirements
Data-level encryption:
- Encrypt IP at rest and in transit
- Keys managed separately from data
- Encryption follows data across systems
Data access controls:
- Role-based access to IP
- Just-in-time privilege elevation
- Continuous authorization checking
Data loss prevention:
- Monitor for unusual data access patterns
- Block bulk downloads of sensitive files
- Alert on exfiltration attempts
When building the CIAM platform, we encrypted customer data at the database level. If attackers stole the database, they got encrypted data without keys.
The same principle applies to trade secrets: protect the data itself, not just the systems containing it.
2. Zero Trust for Intellectual Property
Zero trust principles applied to IP:
Never trust, always verify:
- No implicit trust for any user or system
- Continuous authentication and authorization
- Verify every access request
Least privilege:
- Minimum access needed for job function
- Time-limited access grants
- Regular privilege reviews and revocations
Assume breach:
- Design for post-compromise containment
- Limit lateral movement
- Segment sensitive IP from general systems
Microsegmentation:
- Isolate IP repositories
- Separate development/production environments
- Network segmentation for sensitive data
Implementation example:
For Nike's design systems:
- Designers get access only to their projects (not entire catalog)
- Access expires after project completion
- Downloads logged and monitored
- Bulk exports require approval
This won't prevent all theft, but it limits the blast radius.
3. Vendor Risk Management That Works
Current approach: Annual security questionnaire, checkbox compliance
Better approach: Continuous vendor security monitoring
Before integration:
- Security assessment (not just questionnaire)
- Penetration testing of integration points
- Data flow mapping (what vendor can access)
- Contract provisions (security requirements, audit rights, breach notification)
During integration:
- Least-privilege API access
- Dedicated credentials (not shared admin accounts)
- Network segmentation (vendor systems isolated)
- Activity monitoring (log all vendor actions)
Ongoing:
- Quarterly security reviews
- Real-time threat intelligence (vendor compromises)
- Access audits (disable unused integrations)
- Security rating services (third-party vendor assessment)
When vendor changes:
- Revalidate security if acquired
- Revoke access if security degrades
- Migrate to alternative if vendor can't meet standards
Nike's attack likely came through vendor. Better vendor management might have prevented it.
4. Behavioral Analytics and Anomaly Detection
Traditional security: Signature-based detection (looking for known threats)
Modern requirement: Behavioral analytics (looking for unusual patterns)
What to monitor:
Data access patterns:
- User accessing unusual datasets
- Bulk downloads of IP
- Access outside normal working hours
- Accessing competitors' files (if segmented)
Network patterns:
- Large data transfers to external destinations
- Encrypted tunnels to unknown IPs
- Data exfiltration to cloud storage
- Unusual bandwidth consumption
User behavior:
- Privilege escalation attempts
- Lateral movement across systems
- Accessing unrelated business units
- Downloading entire repositories
The goal: Detect the reconnaissance and exfiltration phases BEFORE ransomware deploys.
Nike likely had alerts firing during the exfiltration period. The question is whether anyone noticed and investigated in time.
When building the CIAM platform, we implemented behavioral analytics that flagged:
- API access spikes (potential data scraping)
- Unusual authentication patterns (credential stuffing)
- Bulk data exports (potential exfiltration)
Many alerts were false positives, but some were real attacks we stopped.
5. Incident Response That Assumes Data Theft
Traditional IR playbook:
- Detect ransomware
- Isolate infected systems
- Restore from backups
- Resume operations
Modern IR playbook:
- Detect ransomware
- ASSUME data exfiltration occurred
- Conduct forensic analysis (what was accessed?)
- Assess IP theft (what trade secrets exposed?)
- Notify stakeholders (customers, partners, regulators)
- Mitigate competitive harm (accelerate product launches, change strategies)
Nike's response should include:
- Forensic timeline (when did exfiltration start?)
- Data inventory (what IP was accessed?)
- Competitive analysis (what advantage did competitors gain?)
- Business strategy adjustment (invalidate stolen roadmaps)
- Legal action (if competitors use stolen IP)
The ransomware is the visible symptom. The data theft is the underlying disease.
What Companies Should Do Now
If you have intellectual property worth protecting (and most companies do), here's your action plan:
1. Inventory your IP
Identify trade secrets:
- Product designs and specifications
- Manufacturing processes
- Source code and algorithms
- Customer lists and contracts
- Supplier agreements
- R&D roadmaps
- Marketing strategies
Document where IP lives:
- What systems contain each asset?
- Who has access?
- Is it encrypted?
- How is it backed up?
- What vendors can access it?
Red flag: If you can't answer these questions, you can't protect IP.
2. Assess current protection
For each IP asset, evaluate:
- Is it encrypted at rest?
- Is access logged and monitored?
- Are downloads restricted?
- Is it on systems with internet exposure?
- Can vendors access it?
Grade each asset: Protected / Partially Protected / Unprotected
Priority: Unprotected high-value IP needs immediate attention.
3. Review vendor access
For each vendor with system access:
- What data can they access?
- Why do they need it?
- Is access monitored?
- When was security last assessed?
- What's their breach history?
Immediate revocations:
- Vendors who don't need current access
- Over-privileged vendor accounts
- Unused integrations
- Vendors with recent security incidents
This Quarter Actions
4. Implement data-level encryption for IP
Don't just encrypt systems. Encrypt the IP itself.
Implementation:
- Database encryption for IP repositories
- File-level encryption for sensitive documents
- Key management infrastructure (HSMs)
- Separate encryption keys by IP classification
The goal: Stolen data is useless without keys.
5. Deploy behavioral analytics
Monitor for exfiltration patterns:
- Unusual data access (volume, time, user)
- Bulk downloads
- Transfers to external destinations
- Use of encryption tools (potential data staging)
Tools to evaluate:
- SIEM with behavioral analytics
- UEBA (User and Entity Behavior Analytics)
- DLP (Data Loss Prevention)
- Network traffic analysis
Start with highest-value IP, expand coverage over time.
6. Implement zero-trust for IP access
Pilot program for most sensitive IP:
- Microsegment IP repositories
- Implement just-in-time access
- Require multi-factor authentication
- Log every access event
- Alert on anomalies
Expand to all IP systems over 12-24 months.
Long-Term Strategic Actions
7. Build IP-focused incident response
Expand IR playbook to include:
- Data exfiltration forensics
- IP theft assessment
- Competitive impact analysis
- Business strategy adjustment
- Legal recourse options
Run tabletop exercises:
- Scenario: 500GB of product roadmaps stolen
- Who needs to be notified?
- What business decisions change?
- How do you mitigate competitive harm?
8. Create IP protection program
Dedicated focus on trade secrets:
- Designated IP protection officer
- Cross-functional team (IT, legal, business)
- Regular IP audits
- Protection roadmap
- Metrics and KPIs
This isn't just IT security. It's business risk management.
9. Pursue legal and technical countermeasures
Legal:
- Trade secret protection agreements (employees, vendors)
- Non-compete and non-disclosure enforcement
- Patent filings (convert trade secrets to patents where appropriate)
- Legal action against IP theft
Technical:
- Digital watermarking (trace leaked documents)
- Honeypot IP (fake secrets that alert if accessed)
- Deception technology (fake databases that detect intrusions)
The goal: Make IP theft detectable and legally actionable.
When building the CIAM platform, we treated our authentication architecture as crown-jewel IP. We encrypted it, limited access, monitored usage, and had legal protections in place.
Every company with competitive IP should do the same.
The Bottom Line
Nike's 1.4TB IP theft shows that ransomware has evolved from system encryption to industrial espionage with encryption as leverage.
What happened:
- Attackers infiltrated Nike's systems (likely via vendor)
- Spent weeks exfiltrating 1.4TB of intellectual property
- Deployed ransomware as cover and additional pressure
- Demanded payment for both decryption AND data non-disclosure
What was stolen:
- Shoe designs and prototypes (years of R&D)
- Manufacturing processes (competitive advantage)
- Supplier contracts (cost structures, pricing)
- Patent applications (innovations)
- Marketing strategies (launch plans)
Why this matters:
- Trade secrets can't be restored from backups
- IP has value to competitors (worth more than ransom)
- Damage extends for years (not just incident period)
- Once disclosed, trade secret protection is lost forever
The evolution:
- Traditional ransomware: Pay to decrypt (restore from backup = problem solved)
- Double extortion: Pay to decrypt AND prevent data leak (backups don't help)
- Modern target: Intellectual property over system access
What needs to change:
For companies:
- Data-centric security (encrypt IP itself, not just systems)
- Zero-trust for IP (continuous verification, least privilege)
- Vendor risk management (continuous monitoring, not annual checkbox)
- Behavioral analytics (detect exfiltration before ransomware)
- IP-focused incident response (assume data theft, assess competitive impact)
For security teams:
- Inventory and classify IP
- Encrypt high-value trade secrets
- Implement anomaly detection
- Monitor vendor access
- Build IP protection program
For executives:
- IP is not just legal concern—it's security concern
- Trade secrets require dedicated protection
- Incident response must account for data theft
- Competitive intelligence market is real threat
Nike could restore encrypted systems from backups. They can't restore stolen competitive advantage.
That's the modern ransomware threat: not holding your systems hostage, but selling your future to your competitors.
The question every company should ask: What intellectual property do we have that competitors would pay millions for?
Then ask: How are we protecting it?
For most companies, the honest answer is: We're not.
And that's exactly what ransomware groups are counting on.
Key Takeaways
- Nike ransomware attack exfiltrated 1.4TB of IP before deploying encryption—data theft was the real attack
- Double extortion model: pay to decrypt files AND pay to prevent trade secret disclosure to competitors
- Trade secrets can't be restored from backups—once stolen, competitive advantage is permanently lost
- IP theft creates multi-year damage: 2026 designs stolen, competitors launch similar products 2027-2028
- Modern ransomware targets data value over system availability—encryption is leverage, not the objective
- Attackers spend weeks/months inside networks before detection—exfiltration happens silently during reconnaissance
- Average detection time: 207 days—plenty of time to steal terabytes of sensitive data
- Vendor compromise likely entry point—third-party access creates widespread attack surface
- Stolen IP market thriving: Fortune 500 trade secrets worth $500K-$5M, patent applications $100K-$500K
- Contact data compounds breach damage—Nike customer data + AT&T SSNs = complete identity profiles
- Data-centric security needed—encrypt IP itself with separate key management, not just perimeter protection
- Zero-trust for IP: continuous verification, least privilege, microsegmentation for crown-jewel assets
- Behavioral analytics critical—detect unusual data access patterns, bulk downloads, exfiltration attempts before ransomware
- Traditional IR inadequate—must assume data theft, assess competitive impact, adjust business strategy
Protecting intellectual property and trade secrets? My Customer Identity Hub covers zero-trust security architecture, data encryption best practices, and authentication frameworks that apply to both customer data and internal IP.
Need help with AI visibility for your B2B SaaS? GrackerAI helps cybersecurity and B2B SaaS companies get cited by ChatGPT, Perplexity, and Google AI Overviews through Generative Engine Optimization.
Deepak Gupta is the co-founder and CEO of GrackerAI. He previously founded a CIAM platform that scaled to serve 1B+ users globally. He writes about AI, cybersecurity, and digital identity at guptadeepak.com.
*** This is a Security Bloggers Network syndicated blog from Deepak Gupta | AI & Cybersecurity Innovation Leader | Founder's Journey from Code to Scale authored by Deepak Gupta - Tech Entrepreneur, Cybersecurity Author. Read the original post at: https://guptadeepak.com/nikes-1-4tb-ip-theft-when-ransomware-targets-trade-secrets-instead-of-files/