Malicious Code Injection in wulan-28 Package - npm Vulnerability

wulan-28 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-170552: Malicious code in wulan-28 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The wulan-28 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 functionality of wulan-28 is to serve as a tool for developers, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the wulan-28 package stems from its inclusion in a malicious campaign that generates and publishes derivative packages with randomized names. This malicious code modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, thereby polluting the npm registry. The origin of this vulnerability is linked to the tea protocol token rewards, which incentivize the creation of such malicious packages. The ramifications include potential security risks for developers who unknowingly use these packages, as well as damage to the integrity of the npm ecosystem.

How To Fix

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

npm uninstall wulan-28

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 avoid using the wulan-28 package altogether until a secure version is released. Additionally, consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The wulan-28 package has been identified as a malicious entity within the npm ecosystem, posing significant risks to developers. It is essential to stay informed about such vulnerabilities and take proactive measures to secure your projects. Regular updates and audits of your dependencies can help mitigate these risks.

See every vulnerability recorded for wulan-28 →

Share this vulnerability

FAQ

The wulan-28 package is a JavaScript package available on npm, primarily used for development purposes but has been compromised to include malicious code.

You can check if your project is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can use the Vulert playground at Vulert Scanner to analyze your package-lock.json file.

Using the wulan-28 package can lead to security vulnerabilities, including unauthorized modifications to your project's package.json file and potential exposure to malicious scripts.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and avoid using packages from untrusted sources.

If you have already used the wulan-28 package, it is crucial to remove it from your project and update your dependencies. Consider using alternative packages that are verified and secure.

How To Fix

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

npm uninstall wulan-28

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