Critical Malicious Code Vulnerability in published_at Package
Summary
MAL-2026-43: Malicious code in published_at (npm). Affected versions are not published. 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 'published_at' package is an npm module that is typically used for managing timestamps related to publication events in various applications. It is designed to provide developers with a simple way to handle and manipulate date and time information. However, this package has been identified to contain malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the 'published_at' package. This code can compromise the entire system on which the package is installed, allowing unauthorized access to sensitive information, including secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it embeds harmful functionality. Systems running this package should be considered fully compromised, and immediate action is required to mitigate potential damage.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall published_atIf 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
There are no effective workarounds for this vulnerability other than removing the package and securing the system. Ensure that all sensitive data is rotated and that the system is monitored for any unusual activity.
Conclusion
The 'published_at' package has been identified as containing malicious code, posing a significant security threat. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Utilizing monitoring tools like Vulert can help prevent future vulnerabilities.
See every vulnerability recorded for published_at →
FAQ
Immediately remove the package and rotate all sensitive information stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential system compromise.
Regularly monitor your dependencies using tools like Vulert, which can alert you to open-source vulnerabilities in real-time.
While the npm ecosystem is generally reliable, it is crucial to remain vigilant and utilize tools like Vulert to monitor for vulnerabilities.
