Malicious Code Injection in opal-teadev: A Threat to npm Users
Summary
MAL-2025-106739: Malicious code in opal-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
opal-teadev is an npm package that is part of the tea.xyz token reward campaign. This package is designed to facilitate certain functionalities within the tea protocol ecosystem. However, it has been identified as being compromised, containing scripts that can manipulate its own package structure and publish malicious variants, thereby posing a significant risk to developers and users relying on it.
Vulnerability Detail
The vulnerability in opal-teadev stems from malicious code embedded within the package. This code is designed to remove private flags from the package.json file, alter version numbers, and generate random package names that are published to the npm registry. The origin of this issue is linked to a broader campaign that aims to inflate developer reputation scores for token rewards, leading to potential pollution of the npm registry and misuse of developer trust.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall opal-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 remove the opal-teadev package from your project by executing 'npm uninstall opal-teadev'. This will prevent any malicious code from executing while you seek a secure alternative or wait for a patched version.
Conclusion
The opal-teadev package has been compromised with malicious code that poses a significant risk to developers and users. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for opal-teadev →
FAQ
The primary risk is that the malicious code can alter your package.json file, leading to unauthorized changes and potential security breaches.
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.
If an immediate update is not possible, consider removing the package from your project as a temporary measure to mitigate risks.
While specific exploits have not been detailed, the potential for unauthorized package modifications poses a significant risk to users.
Regularly audit your dependencies, use tools like Vulert for monitoring, and stay updated on security advisories related to your packages.
