Malicious Code Injection in living_loon_z3n: A Threat to npm Packages

living_loon_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105286: Malicious code in living_loon_z3n (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The living_loon_z3n 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. These packages often contain scripts designed to manipulate package metadata and inflate developer reputation scores, posing a significant risk to the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in living_loon_z3n stems from its malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior is designed to create and publish numerous derivative packages, polluting the npm registry and potentially leading to reputation damage for legitimate developers. The malicious payload is part of a broader scheme to exploit the npm ecosystem for token rewards, making it a serious concern for developers relying on this package.

How To Fix

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

npm uninstall living_loon_z3n

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 manually check your package.json file for any unauthorized changes and revert them. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. 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 living_loon_z3n package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry with unauthorized packages. Developers are urged to remove this package and utilize monitoring tools like Vulert to safeguard their projects against similar vulnerabilities.

See every vulnerability recorded for living_loon_z3n →

Share this vulnerability

FAQ

living_loon_z3n is an npm package that has been identified as malicious, associated with a token reward campaign that floods the npm registry.

The malicious code modifies your package.json file, potentially leading to unauthorized changes and the publication of derivative packages that can harm your project's reputation.

You should remove the living_loon_z3n package from your project immediately and monitor your package.json for any unauthorized changes.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall living_loon_z3n

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