Welcome back to the Scinary Information Nexus! While Richard Martin is away, Brazos Wortham, Joseph Hamilton, and Mario Ortiz take the helm. They crack open some Texas Meadworks blackberry melomel to break down the 2026 Verizon Data Breach Investigations Report (DBIR).

The crew talks about a massive shift in the industry: vulnerability exploitation has officially overtaken credential abuse. We also talk about "vibe coding" -- developers using AI to write code they don't fully understand. This trend causes up to 62% of AI-generated code to ship with vulnerabilities.

Plus, we debunk Hollywood myths about polymorphic AI malware and see how threat actors actually use AI to draft phishing emails and speed up attacks. We review the surprising drop in ransomware payments, noting that 69% of victims now refuse to pay.

What happens when the money dries up? The guys predict a pivot toward public website defacement and data destruction from groups like Shiny Hunters. They also share practical advice on risk-based vulnerability management.

In this episode, we discuss:

• What the 2026 Verizon DBIR reveals about initial access vectors.
• A disastrous DIY absinthe experiment involving wormwood and gin.
• How "vibe coding" is flooding code repositories with vulnerabilities.
• The truth about AI malware and how attackers actually weaponize it.
• The patching ceiling: why organizations tap out at fixing just 30-40% of vulnerabilities in the first week.
• Why 69% of ransomware victims refuse to pay.
• A pro-tip for reading the DBIR without giving up your personal data.

What's your biggest takeaway from this year's DBIR? Let us know in the comments below!

Connect with Scinary Cybersecurity:
https://www.scinary.com
https://x.com/scinarycyber
https://www.linkedin.com/company/scinarycyber/

00:00 Intro
05:15 Blackberry Melomel & DIY Gin
09:45 Exploits Overtake Credential Abuse
15:30 Vibe Coding & AI Threats
33:00 The Limits of Patching
58:30 Declining Ransomware Payments

Welcome back to the Scinary Information Nexus! Pour yourself some mead (or a Texas ale) and join the crew as we tackle some heavy cybersecurity news hitting the K-12 and higher-ed worlds.

This week, Richard Martin, Brazos Wortham, Joseph Hamilton, and Mario Ortiz break down the fallout from the Instructure (Canvas) breach. Threat group Shiny Hunters reportedly exploited a cross-site scripting vulnerability, leading to a massive, undisclosed ransom payment. Now, school districts are stuck in a regulatory nightmare: how do you report a breach when you don't even know what student data was compromised?

We also talk about the debate over state bans on Chinese-owned technology like Lenovo. While Texas Cyber Command maintains a strict Prohibited Technologies list for state agencies, Lenovo currently remains unbanned despite federal security warnings.

We look at the reality of outright hardware bans versus just blocking network traffic. Plus, we clear up the dangerous confusion between Lenovo-owned Motorola Mobility and American-owned Motorola Solutions (which emergency services use). Expanding these state mandates could be a devastating financial hit to public schools already dealing with budget deficits.

In this episode, we discuss:

• How Shiny Hunters breached Instructure via a "Free for Teacher" account
• The regulatory nightmare of reporting K-12 data breaches
• Why easily guessable passwords make brute-forcing simple
• Texas Cyber Command's recent updates to the Prohibited Technologies list
• The danger of banning network domains instead of replacing vulnerable hardware
• Why confusing Motorola Mobility with Motorola Solutions could panic police and emergency services
• How state mandates impact independent school districts that are already struggling

Does the state's approach to cybersecurity actually make schools less secure? Let us know your thoughts in the comments!

Connect with Scinary Cybersecurity:
https://www.scinary.com
https://x.com/scinarycyber
https://www.linkedin.com/company/scinarycyber/

00:00 Intro
02:15 The Canvas Ransomware Breach
34:15 Texas Cyber Command's Lenovo Ban

Welcome back to the Scinary Information Nexus! We kick off a rainy Texas Friday with some Blackberry Melomel from Texas Meadworks and a little banter before getting into some wild government tech news.

This week, Richard, Joseph, Mario, and Brazos break down some highly unusual, militaristic solicitations from the newly formed Texas Cyber Command. What does it mean to establish "operational maneuver" or take back "sovereign IP terrain"? We translate the military jargon into standard cybersecurity terms and look at the reality of this massive, $100+ million project to build a centralized data lake for state endpoints.

We talk through the privacy concerns, the "honeypot" risk of building a single massive data repository, and whether mega-contractors like Palantir are the real winners.

Later, we look at the open-source supply chain hacks hitting platforms like NPM, PyPI, and Docker Hub. We discuss how malicious package updates quietly scrape API keys, the conspiracy theories behind Team PCP, and why the trend of vibe coding makes dependency management more dangerous than ever. If you're a developer, you might want to double-check what you're deploying.

In this episode:

• Tasting Texas Meadworks Blackberry Melomel
• Decoding Texas Cyber Command's aggressive solicitations
• The reality of the estimated $100M+ state data lake and endpoint logging RFP
• The privacy implications and honeypot risks of a centralized state cybersecurity solution
• How open-source supply chain attacks on Docker Hub, PyPI, and NPM work
• Why AI-assisted vibe coding creates a dependency management nightmare
• The urgent need for developers to fork and audit dependencies

Drop your thoughts in the comments: are centralized government data lakes a security necessity or a massive privacy risk?

Connect with Scinary Cybersecurity:
https://www.scinary.com
https://x.com/scinarycyber
https://www.linkedin.com/company/scinarycyber/