Malicious Code Injection in adilzaki Package: A Threat to npm Users

adilzaki Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170663: Malicious code in adilzaki (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The adilzaki package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with malicious packages. The primary function of adilzaki, like many others in this campaign, is to manipulate developer reputation scores through the automatic generation and publication of derivative packages.

Vulnerability Detail

The vulnerability in the adilzaki package stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is designed to inflate developer reputation scores for token rewards, leading to pollution of the npm registry. The malicious payload can introduce security risks by allowing unauthorized access and manipulation of package data, potentially affecting any projects that depend on this package.

How To Fix

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

npm uninstall adilzaki

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 remove the adilzaki package from your project by executing 'npm uninstall adilzaki'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The adilzaki package poses a significant risk due to its malicious code that alters package metadata and can compromise project security. It is crucial for developers to stay informed about such vulnerabilities and take appropriate actions to secure their applications.

See every vulnerability recorded for adilzaki →

Share this vulnerability

FAQ

The adilzaki package is a JavaScript package in the npm ecosystem, primarily associated with the tea.xyz token reward campaign, which has been linked to malicious activities.

The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising the integrity and security of your application.

If you have installed the adilzaki package, it is recommended to uninstall it immediately and monitor for any updates or patches from the package maintainers.

Yes, Vulert can monitor your project for open-source vulnerabilities using just the package-lock.json file, providing real-time alerts without requiring code access.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by the adilzaki 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 adilzaki

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