Critical Malicious Code Vulnerability in spark-ar-jest-mocks Package
Summary
MAL-2026-147: Malicious code in spark-ar-jest-mocks (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 spark-ar-jest-mocks package is a JavaScript library used in testing applications that utilize Spark AR. It provides mock implementations for Jest, a popular testing framework. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed, making it a significant risk for developers and organizations relying on it.
Vulnerability Detail
The vulnerability originates from the inclusion of malicious code within the spark-ar-jest-mocks package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it embeds harmful functionalities within the software. The ramifications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spark-ar-jest-mocksIf 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
Currently, there are no effective workarounds to mitigate the risks associated with the spark-ar-jest-mocks package. The only safe approach is to uninstall the package entirely.
Conclusion
The spark-ar-jest-mocks package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to uninstall the package and secure any affected systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for spark-ar-jest-mocks →
FAQ
You should uninstall the spark-ar-jest-mocks 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 any signup.
Failing to remove the package can lead to unauthorized access to sensitive data, potentially resulting in data breaches and loss of control over your systems.
Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.
Yes, you can continue to use Jest for testing. Consider using alternative mocking libraries that do not pose security risks.
