Protestware: How Ideologically Motivated Attackers Compromise Open Source Code and Supply Chains
Protestware has emerged as a serious supply chain threat in open source ecosystems, where maintainers intentionally embed destructive or politically motivated code into libraries and packages.
Unlike conventional malware aimed at financial profit, protestware is driven by ideological, social, or political motives. It can delete or corrupt data, sabotage business processes, restrict users from specific regions, or spread unauthorized messages.
The risk is comparable to traditional vulnerabilities, repository compromises, and Dependency Confusion attacks because the malicious code often arrives through normal dependency updates.
Known Incidents
One prominent case involved the packages node-ipc and peacenotwar. The node-ipc library added peacenotwar as a dependency; the module checked the user’s IP via geolocation services and, if located in Russia or Belarus, replaced files on disk with heart symbols while creating a WITH-LOVE-FROM-AMERICA.txt file on the desktop.
Another incident affected the popular colors.js library. An infinite loop printing non-ASCII characters was introduced, causing denial of service for any CLI or server application that required the package.
The es5-ext package, used by webpack, contained logic that triggered 100% CPU usage in an infinite loop if the system time was between 22:00 and 06:00 or the locale was set to ru_RU.
Placement and Triggers
Malicious logic can reside in runtime code, npm lifecycle hooks, build scripts, test scripts, or package metadata that fetches instructions from remote servers. Activation conditions include IP geolocation, system locale, environment variables such as NODE_ENV, hostname, username, and specific dates or times.
Detection and Mitigation
Organizations can detect suspicious components through static analysis for geo-IP or file-deletion patterns, dynamic analysis in isolated sandboxes, and continuous monitoring of repository changes. Recommended controls include pinning dependency versions, maintaining an internal artifact repository with approval gates, signing artifacts, and following the NIST Secure Software Development Framework, SLSA levels, and OpenSSF Scorecard assessments.
Related articles
CrowdSec Confirms Theft of Source Code from Roughly 300 GitHub Repositories via TanStack Supply Chain Attack
French cybersecurity firm CrowdSec has confirmed that attackers stole source code from approximately 300 GitHub repositories, including around 170 private ones. The breach occurred in May 2026 through a compromised TanStack component that exfiltrated an API key with read access to the private codebase. The stolen material included code for the company's SaaS console, AWS procedures, connectors, and automation tools, while the remaining repositories contained already-public open source code. No customer data, passwords, organization details, tokens, or other secrets were included in the leak, and all potentially affected credentials were immediately rotated. CrowdSec stated that the code is tightly integrated with internal systems and has largely changed over the past four months, reducing its usefulness outside the company's environment. The SaaS service code undergoes regular audits, and the company sees no immediate threat from the exposure while the investigation continues.
Dependency Confusion Attacks Let Attackers Hijack Internal Library Names in Corporate Builds
A widespread supply chain risk allows attackers to publish packages with internal company names on public registries such as npm and PyPI, causing build systems to pull malicious versions instead of internal ones. The attack works because package managers treat multiple registries as a single list and select the highest version number, with no inherent priority for internal sources. Researcher Alex Birsan demonstrated the technique in February 2021 by registering names harvested from open repositories and error messages, successfully injecting packages into builds at Microsoft, Apple, PayPal, Shopify, Netflix, Tesla and Uber. The malicious code executes during installation because setup scripts and lifecycle hooks run with the privileges of the build agent, exposing environment variables, tokens and internal network access. Mitigation requires a single internal proxy repository that never mixes public responses for internal package names, scoped namespaces bound to private registries, lock files with content hashes, and disabling install scripts where possible. The technique remains effective against any organization that lists both internal and public registries in its build configuration.
NEOMSA ESB Release Strengthens Supply Chain Security Through SBOM and Dependency Hardening
Neoflex has released a new version of its NEOMSA ESB integration platform with a primary focus on cleaning up the software bill of materials and eliminating critical and high-severity vulnerabilities. The team automated SBOM generation using CycloneDX, ran SCA scans with Grype and OWASP Dependency-Check, and performed SAST and secret scanning across all build pipelines. Instead of blindly updating to the latest versions, engineers applied minimal fixed versions for each advisory while handling complex cases involving transitive dependencies, locked files, and deprecated build tools. The effort reduced the total package count from 5,872 to 1,683 after migrating the frontend build to Vite in Camel Karavan 4.18. Remaining medium and low findings were tracked in DefectDojo with clear remediation timelines. The changes deliver measurable risk reduction for on-premise deployments in critical infrastructure and financial organizations.
CodeScoring Launches CodeScoring.Save Artifact Repository for Secure Enterprise Development
CodeScoring has introduced its own artifact storage solution called CodeScoring.Save, designed to handle packages, libraries, container images, and other software components used in development. The product targets corporate users of any size seeking a predictable and resilient repository that integrates security checks directly into storage and distribution workflows. Built in Go for modern Kubernetes environments, Save supports multiple package formats including Maven, npm, NuGet, PyPI, Go Modules, Docker/OCI, DEB, and RPM while providing proxy access to external repositories. It features role-based access, auditing, independent scaling of compute and storage layers, and native integration with CodeScoring.OSA to surface vulnerability data inside the repository itself. The company positions Save as a standalone local deployment option that can operate independently or alongside its existing OSA Proxy module to block malicious components at the repository level. Future plans include support for AI models as artifacts, starting with storage and distribution for ecosystems such as Hugging Face, along with certification for Russian secure development requirements.