Malicious Code Detected in @ivy-shared-components/testing: Security Risk Alert
Summary
MAL-2025-6031: Malicious code in @ivy-shared-components/testing (npm). Affects @ivy-shared-components/testing versions >= 99.99.990. 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 @ivy-shared-components/testing package is a component library designed for use in web applications, providing shared functionalities and utilities for developers. However, it has been identified as having a serious security vulnerability that allows it to communicate with a domain associated with malicious activities, potentially compromising user data and application integrity.
Vulnerability Detail
The vulnerability originates from the package's ability to connect to a malicious domain, which can lead to unauthorized data access, data exfiltration, or other harmful actions. This issue is particularly concerning as it can affect any application utilizing this package, exposing it to various security threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @ivy-shared-components/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 temporary workaround, you may consider removing the @ivy-shared-components/testing package from your project until a secure version is released. You can do this by executing: npm uninstall @ivy-shared-components/testing.
Conclusion
The @ivy-shared-components/testing package has been identified as having a serious vulnerability that allows it to connect to a malicious domain. It is crucial for developers to update the package or remove it to safeguard their applications from potential threats. Utilizing tools like Vulert can help in monitoring and managing such vulnerabilities effectively.
See every vulnerability recorded for @ivy-shared-components/testing →
FAQ
The vulnerability allows the package to communicate with a domain linked to malicious activities, posing a risk to application security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner.
If immediate updates are not feasible, consider removing the package as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the potential for data compromise exists due to the package's communication with malicious domains.
Detailed information can be found in the vulnerability report on GitHub: https://github.com/ossf/malicious-packages/blob/main/osv/malicious/npm/@ivy-shared-components/testing/MAL-2025-6031.json.
