CVE-2022-673: Malicious code in @tsers/react (npm)
Summary
MAL-2022-673: Malicious code in @tsers/react (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 @tsers/react package is an open-source library for building user interfaces in React. It provides various components and utilities to simplify the development process. However, the package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.
Vulnerability Detail
The malicious code in @tsers/react has been identified as a serious threat. It is recommended to consider any computer with this package installed as fully compromised. The code may grant outside entities full control of the computer, potentially exposing sensitive information such as secrets and keys. Immediate action is required to rotate all affected secrets and keys from a different computer. Although removing the package is advised, it cannot guarantee the complete removal of all malicious software resulting from its installation.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @tsers/reactIf 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 is no known workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue.
Conclusion
The presence of malicious code in the @tsers/react package poses a significant security risk. It is crucial to take immediate action by rotating secrets and keys, removing the package, and conducting a thorough security audit. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for @tsers/react →
FAQ
The impact of this vulnerability is severe, as it can lead to the compromise of sensitive information and the potential takeover of the affected computer by outside entities.
You can use the Vulert Playground at Vulert Scanner to check if your computer is affected by this vulnerability. No signup is required, and it utilizes package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
While removing the @tsers/react package is advised, it cannot guarantee the complete removal of all malicious software resulting from its installation. A thorough security audit is recommended to ensure no other malicious software is present.
If your computer is affected, it is crucial to rotate all secrets and keys stored on that computer from a different, secure computer. Additionally, follow the steps provided to remove the @tsers/react package and conduct a thorough security audit.
Yes, the fix for this vulnerability involves rotating affected secrets and keys, removing the @tsers/react package, and conducting a security audit to ensure no other malicious software is present.
