Malicious Code Vulnerability in env-workflow-test Package
Summary
MAL-2026-1725: Malicious code in env-workflow-test (npm). Affects env-workflow-test versions 2.1.10 – 2.1.9. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The env-workflow-test package is an npm library designed for testing workflows in various environments. It is commonly used in CI/CD pipelines to automate testing processes. However, this package has been identified as containing malicious code, which poses significant risks to users who integrate it into their applications.
Vulnerability Detail
The vulnerability originates from malicious code embedded within specific versions of the env-workflow-test package. This code can execute harmful actions on the user's system, potentially leading to data breaches, unauthorized access, or system compromise. The affected versions include 2.1.4 through 2.1.23, which may allow attackers to exploit the package and execute arbitrary code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall env-workflow-testIf 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, users can remove the env-workflow-test package from their project until a secure version is confirmed. This can be done using the following command: npm uninstall env-workflow-test. Consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The env-workflow-test package has been identified as containing malicious code in several versions, posing significant risks to users. It is crucial to update to a patched version or remove the package entirely to mitigate these risks. Regular monitoring of dependencies using tools like Vulert can help maintain security in your applications.
See every vulnerability recorded for env-workflow-test →
FAQ
Versions 2.1.4 to 2.1.23 of the env-workflow-test package are affected by this vulnerability.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If immediate updates are not possible, consider removing the package temporarily and using alternative solutions until a secure version is available.
Using the affected package can lead to data breaches, unauthorized access, and potential system compromise due to the execution of malicious code.
More information can be found in the vulnerability report on the GitHub repository of malicious packages or by consulting security advisories related to npm packages.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
