Critical Malicious Code Vulnerability in @test1230504/test-publish-verify Package
Summary
MAL-2026-16469: Malicious code in @test1230504/test-publish-verify (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 @test1230504/test-publish-verify package is an npm module designed for publishing and verifying test packages. It is commonly used in JavaScript applications to manage package dependencies. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the @test1230504/test-publish-verify package. This code compromises the security of any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to full control of the affected system by an external entity. Users are advised to treat any system with this package installed as fully compromised.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @test1230504/test-publish-verifyIf 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 workaround, ensure that all secrets and keys stored on the affected system are rotated immediately from a different, secure computer. This action helps mitigate the risk of unauthorized access to sensitive information.
Conclusion
The @test1230504/test-publish-verify package contains malicious code that poses a serious security threat. Users must act swiftly to remove the package and secure their systems. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for @test1230504/test-publish-verify →
FAQ
You should remove the package immediately and rotate any secrets or keys stored on the affected system.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring any signup.
Failing to address this vulnerability may result in unauthorized access to your system, leading to data breaches and loss of sensitive information.
Currently, there is no patch available for the @test1230504/test-publish-verify package. The best course of action is to remove the package entirely.
It is advisable to exercise caution with any packages from the same author until they have been thoroughly reviewed for security vulnerabilities.
