Malicious Code Injection in aozalm-devapptea Package - npm Vulnerability

aozalm-devapptea Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-99499: Malicious code in aozalm-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 aozalm-devapptea package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. These packages are designed to inflate developer reputation scores for token rewards. The package's functionality is compromised due to malicious scripts that manipulate its metadata and publish behavior.

Vulnerability Detail

The vulnerability originates from the aozalm-devapptea package, which contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially harming developers' reputations and project integrity.

How To Fix

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

npm uninstall aozalm-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 temporary workaround, you can prevent the installation of the aozalm-devapptea package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will help avoid any unintended installations until the package is removed.

Conclusion

The aozalm-devapptea package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your project and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your open-source projects.

See every vulnerability recorded for aozalm-devapptea →

Share this vulnerability

FAQ

The aozalm-devapptea package is part of a token reward campaign that has been associated with malicious activities on the npm registry.

The malicious code modifies your package metadata and can lead to the pollution of the npm registry, affecting your project's integrity and reputation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you have installed the aozalm-devapptea package, you should uninstall it immediately using 'npm uninstall aozalm-devapptea' and review your project's dependencies for any other vulnerabilities.

Currently, there are no patches available for the aozalm-devapptea package. The best course of action is to remove the package entirely.

How To Fix

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

npm uninstall aozalm-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