Malicious Code Injection in wzkbyd-devapp: A Threat to npm Ecosystem

wzkbyd-devapp Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-111047: Malicious code in wzkbyd-devapp (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 package wzkbyd-devapp is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the distribution of software and enhance developer reputation through token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability in wzkbyd-devapp originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This not only affects the integrity of the package but also poses a risk to developers who may unknowingly use these compromised packages.

How To Fix

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

npm uninstall wzkbyd-devapp

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 wzkbyd-devapp package from your project by executing: npm uninstall wzkbyd-devapp. This will prevent any potential exploitation of the vulnerability until a secure version is available.

Conclusion

The wzkbyd-devapp package has been identified as containing malicious code that poses a significant threat to the npm ecosystem. It is crucial for developers to be aware of this vulnerability, take necessary actions to update or remove the package, and utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for wzkbyd-devapp →

Share this vulnerability

FAQ

wzkbyd-devapp is an npm package associated with the tea.xyz token reward campaign, designed to enhance developer reputation through token rewards.

The package contains scripts that modify package.json files, remove private flags, and generate random package names, leading to the pollution of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

If you have installed wzkbyd-devapp, it is recommended to uninstall it immediately and check for any updates or patches that may be released.

Vulert uses the package-lock.json file to monitor and alert for open-source vulnerabilities in your software, providing real-time insights without needing access to the code.

How To Fix

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

npm uninstall wzkbyd-devapp

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