Critical Malicious Code Vulnerability in mark-testing Package
Summary
MAL-2025-5706: Malicious code in mark-testing (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 mark-testing package is an npm library designed for testing purposes within JavaScript applications. It is commonly used by developers to facilitate various testing scenarios. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on, leading to potential data breaches and unauthorized access.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the mark-testing package. This code can fully compromise any computer that has the package installed, allowing attackers to gain control over the system. The ramifications include unauthorized access to sensitive information, such as secrets and keys, which could lead to further exploitation of the affected system. Given the nature of the malicious code, simply removing the package may not eliminate all traces of the compromise, as additional malware could have been installed.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall mark-testingIf 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 the mark-testing package is not used in any production environment. If you must use it for testing, consider isolating the environment and monitoring it closely for any suspicious activity.
Conclusion
The mark-testing package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for mark-testing →
FAQ
Immediately remove the mark-testing package and rotate any sensitive information stored on the affected system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
Keeping the mark-testing package can lead to unauthorized access to your system, data breaches, and potential further exploitation by attackers.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities using just your package-lock.json file.
After removing the package, ensure to rotate all secrets and keys and monitor your system for any unusual activity.
