Malicious Code Injection in wulan-14: A Threat to npm Ecosystem

wulan-14 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170538: Malicious code in wulan-14 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The package wulan-14 is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the development and sharing of JavaScript code. However, wulan-14 has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages that inflate developer reputation scores for token rewards. This vulnerability poses a significant risk to developers and users relying on the integrity of npm packages.

Vulnerability Detail

The vulnerability in wulan-14 originates from its association with the tea.xyz token reward campaign, which has been linked to malicious activities on npm. The package contains scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This leads to the continuous republishing of variants, effectively polluting the npm registry and compromising the reliability of the ecosystem. The ramifications include potential security risks for applications using these packages, as well as damage to the reputation of legitimate developers.

How To Fix

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

npm uninstall wulan-14

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 wulan-14 and any other packages associated with the tea.xyz token reward campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities in your project.

Conclusion

The discovery of malicious code in the wulan-14 package highlights the importance of vigilance in managing dependencies within the npm ecosystem. By understanding the nature of this vulnerability and taking proactive steps to mitigate risks, developers can protect their applications and maintain the integrity of their projects.

See every vulnerability recorded for wulan-14 →

Share this vulnerability

FAQ

Wulan-14 is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

You can use the Vulert service to monitor your package-lock.json file for vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

You should uninstall wulan-14 immediately using 'npm uninstall wulan-14' and audit your dependencies for any other vulnerabilities.

Yes, tools like Vulert can help monitor and alert you for open-source vulnerabilities in your software without requiring access to the code or installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall wulan-14

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