Malicious Code Injection in then_ocelot_lavender-55 Package
Summary
MAL-2025-109583: Malicious code in then_ocelot_lavender-55 (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 then_ocelot_lavender-55 package is part of the npm ecosystem, typically used for JavaScript development. It is associated with the tea.xyz token reward campaign, which has been linked to a series of malicious packages that flood the npm registry. These packages are designed to manipulate developer reputation scores by automatically generating and publishing derivative packages with randomized names.
Vulnerability Detail
The vulnerability in then_ocelot_lavender-55 stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this issue is traced back to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall then_ocelot_lavender-55If 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 then_ocelot_lavender-55 package until a patched version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The then_ocelot_lavender-55 package contains a significant vulnerability due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to update to a patched version or find alternatives to ensure the security of their projects. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in real-time.
See every vulnerability recorded for then_ocelot_lavender-55 →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, often used in JavaScript development.
The vulnerability can lead to the injection of malicious code, potentially compromising your project's security and integrity.
You should immediately update the package to a patched version or remove it from your project to mitigate risks.
You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without signing up.
