The wake-up call: npm ‘is’ package compromise
In July 2025, the npm package “is”—downloaded millions of times each week—was quietly hijacked. A simple phishing email to its maintainer opened the door for attackers to inject malicious code into the software supply chain, embedding backdoors into thousands of downstream applications.
This incident is more than a one-off breach; it’s a warning shot for the entire open source ecosystem. Even trusted dependencies can become vectors for sophisticated supply-chain attacks. As development pipelines grow increasingly automated, traditional defenses are no longer enough.
To stay secure, organizations must rethink the foundation of their containers themselves. That’s where distroless containers come in—stripping away unnecessary components to eliminate entire classes of vulnerabilities before they can be exploited.
Why traditional containers failed
Traditional containers are built like miniature operating systems. They include shells, package managers, network tools, and other system utilities — many of which are unnecessary for the application but are ideal targets for attackers.
When the malicious ‘is’ package was executed in these environments, it had access to tools to download more payloads, connect to remote servers, and persist in the system. In essence, developers unintentionally shipped a hacker’s toolkit into production.
Distroless: Security through minimalism
Distroless containers flip this paradigm by including only the essentials required to run an application — nothing more. No shell, no package manager, no debugging tools. This results in a dramatically smaller attack surface.
By removing utilities that malware typically depends on, distroless containers don’t just reduce risk — they actively disable entire categories of exploits. In the case of the ‘is’ attack, the malware would have had no shell to execute or tools to abuse. The compromise may still occur, but the impact is neutered.
Taking distroless further: Secure, minimal containers for cloud native workloads
Distroless container images remove package managers, shells, and other non-essential software to shrink the attack surface. Modern distroless practices go a step further:
- Automated, frequent rebuilds with upstream security patches
- Signed Software Bills of Materials (SBOMs) for transparency
- Rigorous vulnerability scanning before release
With these measures, teams can meet high supply-chain integrity standards such as SLSA Level 4. Compared to an industry median of roughly 200 days to patch critical issues, well-maintained distroless pipelines can deliver fixes within days.
Measurable impact
Organizations adopting distroless workflows report:
- Up to 70 % fewer security incidents
- 95 % faster vulnerability remediation
- 50–90 % smaller container images
- Streamlined compliance audits and SBOM reporting
Smaller images also deploy faster, consume less bandwidth, and increase container density, improving both security posture and operational efficiency.
Why it matters
Software supply-chain attacks are becoming more targeted, automated, and well-funded. Distroless strategies help teams stay ahead by eliminating entire classes of vulnerabilities rather than merely patching them after discovery.
Distroless approaches—and solutions such as CleanStart—illustrate how continuous rebuilding, minimal base images, and signed SBOMs can proactively protect modern infrastructure.
Bottom line
Every unnecessary binary is a potential liability. A distroless container—minimal, transparent, and continuously rebuilt—turns that liability into strength.
By adopting distroless practices such as automated rebuilds, signed SBOMs, and minimal base images, teams can move from reactive patching to proactive defense. The path forward is clear: secure your software supply chain from the ground up.
The question isn’t whether another npm-style attack will happen—it’s whether your organization will be ready when it does.