Open Source Security Advisory Update: Wednesday, April 1, 2026 Boston, MA 10:00 AM ET Over the past week, we have nearly finalized our investigation and are now in the final stages of documentation and review. There continues to be no indication that Aqua’s commercial products have been affected. As part of this process, we identified …
The first quarter of 2026 started with a lull and ended with a bang. Early seasonal slowdowns across ransomware deployments, infostealer downloads, and other observed cybercriminal activity gave way to high-profile announcements, politically linked cyberattacks, and AI developments that shaped the cyber threat landscape this quarter.
The Mercor breach and the LiteLLM compromise exposed a blind spot in AI security. This deep technical piece explains how to secure AI data vendors, CI/CD paths, release pipelines, and AI gateways with continuous red teaming and evidence-backed validation.
Cloud attack framework skips cryptomining, harvests financial, messaging, and enterprise credentials for fraud, spam, and potential extortion.
Python Package Index shares insights and provides guidance following LiteLLM/Telnyx supply-chain attacks
Personal notes on systems engineering and IT: guides, deep dives, dissections, and sometimes reflections.
The npm client’s default settings are a root cause of JavaScript’s recurring supply chain security problems.
As of 2:00 PM ET on March 24, 2026
The Trivy Supply Chain Attack shows how security tools can be weaponized. Learn how this 2026 breach unfolded and how Cortex Cloud blocks the threat.
On March 19, 2026, threat actors compromised Aqua Security's CI/CD pipeline and used stolen credentials to push backdoored versions of the aquasec/trivy vulnerability scanner to Docker Hub. A second wave of compromised images followed on March 22. The malicious images contained an infostealer targeting CI/CD secrets, cloud credentials, SSH keys, and Docker configurations. This post summarizes what happened, what Docker did in response, and what you should do if you use Trivy.
Dependencies are a huge supply chain security risk; the more of them you have, and the more often you update, the bigger the attack surface.
Open source components are getting compromised a lot more often. I did some counting, with a combination of searching, memory, and AI assistance, and we had two in 2026-Q1 ( trivy, axios), after four in 2025 ( shai-hulud, glassworm, nx, tj-actions), and very few historically [1]: Earlier attacks were generally compromises of single projects, but some time around Shai-Hulud in 2025-11 there sta
Why npm, pip, and direct Git dependencies can expose your secrets, how the attack works, and which controls actually reduce the blast radius.
Personal site of Marek Šuppa — writing, teaching, and learning.
Breaking down the March 2026 Trivy supply chain attack. TeamPCP compromised trivy + trivy-action & setup-trivy GitHub Actions, deploying credential stealers.
Inside the ways that GitHub Actions' versioning works, and how we improved Renovate's support.