Malicious Code Injection in happy_lizard_white-56: npm Package Vulnerability

happy_lizard_white-56 Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103595: Malicious code in happy_lizard_white-56 (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 'happy_lizard_white-56' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the sharing and reuse of code among developers. However, this package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This vulnerability exposes users to potential security risks as it modifies critical files and repopulates the npm registry with harmful variants.

Vulnerability Detail

The vulnerability in 'happy_lizard_white-56' originates from its association with the tea.xyz token reward campaign. The package contains scripts that automatically modify the package.json file by removing private flags and changing version numbers. Additionally, it generates random package names, which can lead to the pollution of the npm registry. The ramifications of this vulnerability include the potential for developers to inadvertently use compromised packages, leading to security breaches and loss of trust in the npm ecosystem.

How To Fix

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

npm uninstall happy_lizard_white-56

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, consider using a package-lock.json file to lock your dependencies to known secure versions. You can also monitor your dependencies for vulnerabilities using tools like Vulert. For example, you can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The 'happy_lizard_white-56' package poses a significant security risk due to its malicious code designed to manipulate package management processes. It is crucial for developers to be vigilant and take necessary actions to mitigate this vulnerability by removing the affected package and monitoring their dependencies.

See every vulnerability recorded for happy_lizard_white-56 →

Share this vulnerability

FAQ

The impact includes potential exposure to malicious code and the risk of using compromised packages that can lead to security breaches.

You can check your package.json and package-lock.json files for the presence of 'happy_lizard_white-56'.

Yes, you can use tools like Vulert to monitor and alert in real-time for open-source vulnerabilities in your software.

If immediate removal is not possible, ensure to lock your dependencies and monitor for any updates or patches.

More information can be found in the vulnerability report on the GitHub repository for malicious packages.

How To Fix

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

npm uninstall happy_lizard_white-56

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