Malicious Code Vulnerability in scotty-teadev: A Threat to npm Users
Summary
MAL-2025-108435: Malicious code in scotty-teadev (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 scotty-teadev package is part of the npm ecosystem, primarily used for JavaScript development. It is often utilized in various applications to enhance functionality and streamline development processes. However, this package has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to significant security risks for developers and users alike.
Vulnerability Detail
The vulnerability in scotty-teadev originates from its association with the tea.xyz token reward campaign, which has been flooding the npm registry with malicious packages. These packages contain scripts designed to automatically generate and publish derivative packages with randomized names, effectively polluting the npm registry. The malicious payload alters the package.json file by removing private flags, changing version numbers, and continuously republishing variants, which can lead to compromised developer reputations and potential security breaches in applications relying on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall scotty-teadevIf 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 can avoid using the scotty-teadev package until a secure version is released. If you must use it, consider isolating its use in a controlled environment to mitigate potential risks.
Conclusion
The scotty-teadev package poses a significant security risk due to its malicious code designed to exploit the npm registry. Developers should take immediate action to remove the package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help maintain security in open-source projects.
See every vulnerability recorded for scotty-teadev →
FAQ
scotty-teadev is an npm package used in JavaScript development, but it has been identified as part of a malicious campaign.
The vulnerability can lead to the introduction of malicious code into your application, compromising its security and potentially affecting user data.
You should remove the package immediately and check for any updates or patches that may address the vulnerability.
You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can also check your application’s status using the Vulert playground without any signup.
Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
