Malware in cache-section-helper
Malware was discovered in the npm package cache-section-helper. Systems with this package installed or running are considered fully compromised and require immediate remediation.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- cache-section-helper
The npm package cache-section-helper was found to contain malware. According to the GitHub Advisory (GHSA-wg39-m2jm-wxhp), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the compromise.\n\nThis represents a critical supply chain attack through a compromised package in the npm ecosystem.
Indicators of compromise
- Packages
- cache-section-helper
Remediation
- Immediately isolate any system with cache-section-helper installed or running from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the cache-section-helper package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected systems as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-wg39-m2jm-wxhp · GitHub Advisory Database
Cite this entry
"Malware in cache-section-helper." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 2, 2026; last updated July 2, 2026. https://supplychainattack.org/incident/malware-in-cache-section-helper-ir40bi
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in require-i18next (npm)
The npm package require-i18next version 20.0.0 was identified as malicious by the OpenSSF Package Analysis project. The package communicates with domains associated with malicious activity and executes commands associated with malicious behavior.
npmCompromised package - resolvedcritical
Malicious code in akamaijs-sensorv1 (npm)
The npm package akamaijs-sensorv1, which advertises itself as an Akamai Bot Manager sensor generator, contains malicious code that executes hidden dynamic code and fetches remote instructions from a Google Calendar-based command-and-control channel. The package uses invisible Unicode characters to conceal executable code and establishes a covert remote-code execution sink controlled by an attacker-owned email account.
npmCompromised packageMalicious commit - resolvedcritical
Malicious code in @openrepl/shared (npm)
The npm package @openrepl/shared contained malicious code that executed a preinstall hook to exfiltrate the installer's OS username and hostname to an external service (beeceptor.com). The package provided no legitimate functionality and was designed solely for data collection.
npmCompromised package - containedcritical
Malicious code in @wololasod/tiny-id (npm)
The npm package @wololasod/tiny-id contained obfuscated malicious code that downloads and executes platform-specific remote executables on Windows and Linux systems. The dropper was embedded in both the main entry point (dist/index.cjs) and the TypeScript types file (dist/index.d.ts), disguised as a tiny ID generator.
npmCompromised packageMalicious commit