You’re probably not a programmer. However, how your programmers work on software can majorly impact your software development process, particularly regarding security.
Over the past few years, attackers have been able to infiltrate common software packages, specifically through modularity. Shared libraries and open repositories have led to major security issues that, while seemingly small, can bring mission-critical systems to their knees.
This post uses real-world examples, such as the XZ hack and other notable incidents, to highlight the importance of securing the modular programming paradigm.
Understanding Modular Programming
Modular programming is a design technique that breaks down a program into smaller, manageable, and interchangeable modules. This method facilitates easier maintenance, testing, and debugging. It also allows developers to reuse code across different projects, saving time and resources. Common examples of modular programming include libraries, frameworks, and microservices architectures used in various applications.
It’s no understatement to say that this approach is, and has been, the primary driver of software development. It makes building more complex applications easier and eliminates the need for programmers to reinvent the wheel consistently regarding key functions.
Despite its benefits, modular programming is not without its risks.
Attack Surfaces in Modular Programming
In the context of modular programming, the attack surface expands with each additional module integrated into the system. This is due to the dependency on multiple third-party modules, each of which may have vulnerabilities.
For instance, an attacker might target a seemingly secure module widely used in the industry. By exploiting a vulnerability in this module, they can access any system that incorporates it. This is often exacerbated by many developers relying on open-source modules, which may not always be rigorously audited for security flaws.
The interconnectivity between modules can create complex dependency chains, where a vulnerability in a single module can propagate through the entire system. This interconnectedness can make it challenging to identify and isolate the source of a security breach, as the compromised module might be deeply embedded within the application’s architecture.
Case Study: The XZ Hack
One of the most illustrative examples of the dangers of modular programming is the XZ hack. XZ is a popular data compression library used in many software projects. In this incident, attackers compromised the library by inserting malicious code into the module. This code was then propagated to all projects using the XZ library, creating a massive security breach.
The XZ hack was insidious because it exploited developers’ trust in widely used modules. The compromised code allowed attackers to execute arbitrary commands on any infected library system. As a result, sensitive data was exposed, and numerous systems were rendered vulnerable to further attacks.
Other Examples of Modular Library Attacks
The dangers of modular programming are not limited to the XZ hack. Several other high-profile incidents further illustrate the vulnerabilities associated with this approach.
- Event-Stream Incident: Event-Stream, a popular JavaScript library, was compromised when a malicious maintainer added a dependency that contained cryptocurrency-stealing malware. The malware targeted a specific application, Copay, and stole cryptocurrency from unsuspecting users.
- SolarWinds Attack: Perhaps one of the most notorious supply chain attacks, the SolarWinds incident involved inserting malicious code into the company’s Orion software updates. This breach allowed attackers access to numerous high-profile organizations, including government agencies and Fortune 500 companies. The attack exploited the trust in legitimate software updates, demonstrating how modular programming and dependency management can be leveraged for large-scale breaches.
These examples share common patterns: exploitation of trust, insertion of malicious code into widely-used modules, and significant impact due to the widespread use of compromised software.
Mitigating the Risks of Module Supply Chain Threats
These examples highlight how software development and supply chain security quickly become non-negotiable. To mitigate the risks associated with modular programming and reduce attack surfaces, developers and organizations can adopt several best practices:
- Vetting Dependencies: Review and audit third-party modules before integrating them into projects. Use trusted sources and avoid unverified code.
- Regular Updates: Keep all modules and dependencies up to date with the latest security patches and updates. Outdated modules can become easy targets for attackers.
- Monitoring and Alerts: Implement monitoring systems to detect unusual activity or changes in module behavior. Continuous monitoring can help identify potential security threats early.
- Code Reviews: Conduct regular code reviews and security audits to identify and address potential vulnerabilities. Peer reviews can uncover issues that automated tools might miss.
- Minimal Permissions: Apply the principle of least privilege, ensuring modules have only the permissions necessary for their function. Restricting permissions can limit the potential damage from a compromised module. Also, consider zero-trust approaches to security.
- Dependency Management Tools: Utilize tools that help manage and secure dependencies. These tools can automate updates, track changes, and provide alerts for known vulnerabilities.
Keep Your Infrastructure Secure with Lazarus Alliance
While beneficial in many ways, modular programming introduces significant risks by expanding the attack surface within the software supply chain. Most modern businesses cannot wait until the next threat drops before considering how to protect themselves. Lazarus Alliance has you covered, whether to heighten software security or align with requirements like the Secure Software Development Framework.
To learn more, contact us.
- FedRAMP
- StateRAMP
- NIST 800-53
- FARS NIST 800-171
- CMMC
- SOC 1 & SOC 2
- HIPAA, HITECH, & Meaningful Use
- PCI DSS RoC & SAQ
- IRS 1075 & 4812
- ISO 27001, ISO 27002, ISO 27005, ISO 27017, ISO 27018, ISO 27701, ISO 22301, ISO 17020, ISO 17021, ISO 17025, ISO 17065, ISO 9001, & ISO 90003
- NIAP Common Criteria – Lazarus Alliance Laboratories
- And dozens more!
What Is Autonomous Malware?
We’re reaching the end of 2025, and looking ahead to 2026, most experts are discussing the latest threats that will shape the year ahead. This year, we’re seeing a new, but not unexpected, shift to autonomous threats driven by state-sponsored actors and AI. With that in mind, a new generation of threats, broadly known as...Continue reading→
What CISA’s Emergency Directive 26-01 Means for Everyone
In mid-October 2025, the CISA issued one of its most urgent orders yet: Emergency Directive 26-01. The directive calls on all Federal Civilian Executive Branch (FCEB) agencies to immediately mitigate vulnerabilities in devices from F5 Networks following a state-sponsored breach of F5’s systems and access to portions of BIG-IP source code and vulnerability data. The event...Continue reading→
Cybersecurity and Vetting AI-Powered Tools
A recent exploit involving a new AI-focused browser shone a light on a critical problem–namely, that browser security is a constant issue, and AI is just making that threat more pronounced. Attackers discovered a way to use that browser’s memory features to implant hidden instructions inside an AI assistant. Once stored, those instructions triggered unwanted...Continue reading→
Shutdown Security And Cyber Vulnerability
When the federal government shuts down, the public sees closed monuments, unpaid workers, and halted programs. What they do not see is the silent surge of cyberattacks targeting agencies already operating on fumes. During the most recent shutdown, attacks against U.S. government systems spiked by nearly 85%. Cybersecurity failures during government disruptions rarely start with...Continue reading→
Identity and the Shift from Malware
The world of cyber threats is rapidly evolving, and while we can see these changes more generally, it’s always crucial to understand them concretely. As the 2025 CrowdStrike Global Threat Report shows us, the landscape of our industry is changing. We’re digging into this report to discuss a challenging trend: the move of hackers foregoing...Continue reading→
Maintaining Compliance Against Prompt Injection Attacks
The increasing adoption of AI by businesses introduces security risks that current cybersecurity frameworks are not prepared to address. A particularly complex emerging threat is prompt injection attacks. These attacks manipulate the integrity of large language models and other AI systems, potentially compromising security protocols and legal compliance. Organizations adopting AI must have a plan...Continue reading→
Are We Already Talking About CMMC 3.0?
The ink has barely dried on the CMMC final rule, and already the defense contracting community is buzzing with speculation about what comes next. Just when contractors thought they had a moment to catch their breath after years of regulatory limbo, whispers of CMMC 3.0 have begun circulating through the industry. But is this just...Continue reading→
Centralizing Identity-Based Risk
As the traditional network boundary dissolves and remote work becomes standard practice, identities are the major frontier for security. Whether we’re talking about human users, service accounts, or machine identities, these have emerged as both the primary access mechanism and the most targeted attack vector. It has become imperative for providers to centralize identity management...Continue reading→
Deviation and Significant Change Requests in FedRAMP: A Comprehensive Guide
FedRAMP provides a standardized approach to security assessment, authorization, and continuous monitoring for cloud products and services used by federal agencies. While the program’s rigorous baseline requirements ensure consistent security, the reality is that this consistency calls for a little flexibility. This is where deviation requests and significant change requests come into play. These two...Continue reading→
The Costs of Compliance and Data Breaches
Data is possibly one of the most valuable assets any organization holds. Customer information, employee records, and proprietary business intelligence present challenges because the data flowing through modern enterprises represents both significant opportunities and serious risks. Businesses face a challenging balance: investing in compliance measures to protect sensitive information while also preparing for the real...Continue reading→
Related Posts