Malicious Code Exposure in @woodpecker-web-shared/components Package
Summary
MAL-2026-16354: Malicious code in @woodpecker-web-shared/components (npm). Affects @woodpecker-web-shared/components versions 2.20.5. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The @woodpecker-web-shared/components package is a component library designed for use in web applications, providing reusable UI components. However, it has been found to contain a vulnerability that allows malicious code to run during installation, potentially compromising user data and system integrity.
Vulnerability Detail
The vulnerability arises from a postinstall script that executes on npm install, which collects sensitive information about the host system, including hostname, username, platform, architecture, current working directory, Node.js version, and npm lifecycle event. This information is then sent to a hardcoded external server, posing a significant risk of data exfiltration and privacy invasion. The behavior is automatic and does not require user consent, making it a serious security concern.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @woodpecker-web-shared/components
If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, you can avoid using the @woodpecker-web-shared/components package until a fix is confirmed. Alternatively, you can manually remove the postinstall script from the package if you have control over the installation process, although this is not recommended as it may lead to other issues.
Conclusion
The @woodpecker-web-shared/components package contains a serious vulnerability that exposes sensitive information during installation. It is crucial to update to the latest version to mitigate risks. Utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for @woodpecker-web-shared/components →
FAQ
The vulnerability involves malicious code that collects and sends sensitive information to an external server during the installation process.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.
Yes, updating to the latest version of the @woodpecker-web-shared/components package will address the vulnerability.
Consider removing the package or disabling the postinstall script as a temporary measure until you can apply the update.
Failure to address this vulnerability can lead to unauthorized data access, privacy breaches, and potential exploitation of your system.