InfoSec.Watch — Newsletter

🚨 Top Stories

Storm-1175 Deploys Medusa Ransomware at 'High Velocity'

Microsoft says the financially motivated cybercrime group has exploited n-day and zero-day vulnerabilities in campaigns built around speed.

Source: https://www.darkreading.com/threat-intelligence/storm-1175-medusa-ransomware-high-velocity

💡 Key Takeaway: Treat this as a live exploitation risk: identify exposed assets, prioritize emergency remediation, and hunt for signs of compromise before patching closes the window.

Backdoored Smart Slider 3 Pro Update Distributed via Compromised Nextend Servers

Unknown threat actors hijacked the update system for the Smart Slider 3 Pro plugin for WordPress and Joomla to push a poisoned version containing a backdoor. The incident impacts Smart Slider 3 Pro version 3.5.1.35 for WordPress, according to Patchstack.

Source: https://thehackernews.com/2026/04/backdoored-smart-slider-3-pro-update.html

💡 Key Takeaway: Do not leave this as awareness only: turn it into a specific control, detection, or exposure-reduction action before the week is over.

AI-Assisted Supply Chain Attack Targets GitHub

PRT-scan is the second campaign in recent months where a threat actor appears to have used AI for automated targeting of a widespread GitHub misconfiguration.

Source: https://www.darkreading.com/application-security/ai-assisted-supply-chain-attack-targets-github

💡 Key Takeaway: Validate email, endpoint, and egress controls together, then hunt across telemetry for execution chains, persistence, LOLBin abuse, and operator follow-on activity.

🛡️ Vulnerability Spotlight

Analysis of One Billion CISA KEV Remediation Records Exposes Limits of Human-Scale Security

Analysis of one billion CISA KEV remediation records reveals a breaking point for human-scale security. Qualys says most critical flaws are exploited before defenders can patch them.

Source: https://www.bleepingcomputer.com/news/security/analysis-of-one-billion-cisa-kev-remediation-records-exposes-limits-of-human-scale-security/

💡 Key Takeaway: Assume opportunistic exploitation is already underway: patch exposed assets first, review logs for related activity, and verify mitigations are really blocking abuse.

CVE-2026-40175 (CVSS 10): Critical Axios Vulnerability and Exploit Code Disclosed Publicly

A critical CVSS 10 flaw in Axios, CVE-2026-40175, could allow attackers to bypass AWS IMDSv2 and achieve RCE via header injection. Upgrade to v1.15.0 immediately.

Source: https://securityonline.info/axios-vulnerability-cve-2026-40175-cloud-takeover-rce/

💡 Key Takeaway: Prioritize internet-facing and privileged systems first, add exploit-attempt detections, and verify that compensating controls actually block code execution paths.

Adobe Patches Reader Zero-Day Exploited for Months

The vulnerability is tracked as CVE-2026-34621, and Adobe has confirmed that it can be exploited for arbitrary code execution.

Source: https://www.securityweek.com/adobe-patches-reader-zero-day-exploited-for-months/

💡 Key Takeaway: Handle this like an active threat, not routine maintenance: reduce exposure immediately, validate compensating controls, and look for evidence of attempted exploitation.

📈 Trend to Watch

Healthcare IT Solutions Provider ChipSoft Hit by Ransomware Attack

Dutch healthcare software vendor ChipSoft was hit by a ransomware attack that forced the company to take its website and digital services offline for patients and healthcare providers.

Source: https://www.bleepingcomputer.com/news/security/healthcare-it-solutions-provider-chipsoft-hit-by-ransomware-attack/

💡 Key Takeaway: Focus on the full intrusion chain: delivery, execution, persistence, and command-and-control should all be visible in telemetry before this becomes a missed campaign.

🏛️ Policy & Regulation Watch

Data Center Tech Lobbyists Fearmonger in Attempt to Retroactively Roll Back Right to Repair Law

Cisco, IBM, and major lobbying groups are trying to exempt “critical infrastructure” from an existing Colorado law.

Source: https://www.404media.co/data-center-tech-lobbyists-fearmonger-in-attempt-to-retroactively-roll-back-right-to-repair-law/

💡 Key Takeaway: Translate this into a concrete action this week: reduce exposure, improve detection, and validate the control that is supposed to stop this exact failure mode.

Sen. Sanders Talks to Claude About AI and Privacy

The discussion centers on privacy, and Claude appears to perform credibly on the core issues raised.

Source: https://www.schneier.com/blog/archives/2026/04/sen-sanders-talks-to-claude-about-ai-and-privacy.html

💡 Key Takeaway: Use this item to drive one practical change now: shrink the attack surface, tighten monitoring, or validate a control you have been assuming works.

⚡ Quick Hits

China-Linked Storm-1175 Exploits Zero-Days to Rapidly Deploy Medusa Ransomware

A China-linked threat actor tied to Medusa ransomware is combining zero-day and n-day exploitation to compromise internet-facing systems at high speed.

Source: https://thehackernews.com/2026/04/china-linked-storm-1175-exploits-zero.html

💡 Key Takeaway: Treat this as an active exposure-management problem: identify reachable systems, patch or mitigate by risk tier, and review telemetry for evidence of attempted exploitation.

New AI-Driven Phishing Campaign Subverts Microsoft’s Device Code Flow

Microsoft says EvilToken, an AI-powered phishing-as-a-service toolkit, is abusing device code flow to bypass MFA and target high-value accounts.

Source: https://securityonline.info/eviltoken-device-code-phishing-ai-mfa-bypass/

💡 Key Takeaway: Treat this as a behavior problem, not just a malware-name problem: review detections for script execution, trusted-tool abuse, persistence, and outbound connections.

Iranian Threat Actors Disrupt US Critical Infrastructure via Exposed PLCs

Attackers compromised internet-facing OT devices and caused file and display manipulation, operational disruption, and financial losses across sectors.

Source: https://www.darkreading.com/ics-ot-security/iranian-threat-actors-us-critical-infrastructure-exposed-plcs

💡 Key Takeaway: Rank affected assets by exposure and privilege, verify mitigation status, and confirm detections exist for the exploitation path before calling remediation complete.

TP-Link Archer AX53 Hit by Multiple High-Severity Vulnerabilities

TP-Link is urging Archer AX53 v1.0 users to update firmware to fix five critical flaws, including OS command injection and file disclosure issues.

Source: https://securityonline.info/tp-link-archer-ax53-vulnerability-os-command-injection-patch/

💡 Key Takeaway: Remote execution risk means exposure triage comes first: isolate reachable systems, validate blocking controls, and monitor aggressively for exploit activity.

Fortinet Issues Emergency Patch for FortiClient Zero-Day

The authentication bypass flaw, tracked as CVE-2026-35616, is the latest in a series of Fortinet vulnerabilities that have been exploited in the wild.

Source: https://www.darkreading.com/vulnerabilities-threats/fortinet-emergency-patch-forticlient-zero-day

💡 Key Takeaway: Handle this as exposure reduction plus validation: find reachable systems first, apply mitigations by risk, and check telemetry for attempted exploitation.

⚔️ Actionable Defense Move of the Week

One-Week Tier-Zero Validation Loop

For every Tier-Zero patch this week, including firewalls, MDM/EMM, VPN, IAM, and backup platforms: 1) verify the new version on-box, 2) confirm exposure is removed or allowlisted externally, 3) review 14 days of admin, auth, and config logs for anomalies, and 4) rotate secrets if compromise is plausible.

💡 Key Takeaway: Patching is step one—validation plus assumed-breach log review is step two.

🧠 Final Word

Final Word

This week’s stories reinforce that identity paths and trust boundaries remain a primary operational weak point, while software supply chain abuse keeps creating asymmetric risk for defenders. The broader pattern is that active exploitation pressure continues to compress patch and validation timelines. The practical takeaway is to tighten exposed control planes, validate compensating controls, and review telemetry as if exploitation attempts are already in motion.

💡 Key Takeaway: Treat identity paths like production attack surface: reduce exposure, validate every alternate flow, and review auth logs before assumptions become incidents.

Keep Reading