Malicious Code Injection in ozzlvy-devapptea Package

ozzlvy-devapptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106877: Malicious code in ozzlvy-devapptea (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The ozzlvy-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with various packages. These packages often contain scripts designed to automatically publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. This behavior raises significant concerns regarding the integrity and security of the npm registry.

Vulnerability Detail

The vulnerability in the ozzlvy-devapptea package stems from the inclusion of 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 these variants. The malicious payload can significantly pollute the npm registry, posing risks to developers who may unknowingly install compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits the npm ecosystem for malicious purposes.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ozzlvy-devapptea

If 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 workaround, you can avoid using the ozzlvy-devapptea package altogether and look for alternative packages that provide similar functionality without the associated risks. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The ozzlvy-devapptea package contains malicious code that poses significant risks to developers and the integrity of the npm registry. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities to maintain a secure development environment.

See every vulnerability recorded for ozzlvy-devapptea →

Share this vulnerability

FAQ

The ozzlvy-devapptea package is part of a campaign that floods the npm registry with malicious packages designed to inflate developer reputation scores for token rewards.

The malicious code modifies your package.json file, removes private flags, and continuously republishes variants, which can lead to the pollution of the npm registry and potential security risks.

You should uninstall the ozzlvy-devapptea package immediately using the command npm uninstall ozzlvy-devapptea and look for secure alternatives.

You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall ozzlvy-devapptea

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback