Malicious Code Injection in yuni-lapis49-pore: A Threat to npm Packages

yuni-lapis49-pore Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-98556: Malicious code in yuni-lapis49-pore (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

yuni-lapis49-pore is an npm package that has been identified as part of a malicious campaign targeting the npm ecosystem. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package lies in its ability to manipulate package metadata and flood the npm registry with unwanted variants.

Vulnerability Detail

The vulnerability in yuni-lapis49-pore stems from its malicious payload that modifies the package.json file by removing private flags and altering version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly use these tainted packages.

How To Fix

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

npm uninstall yuni-lapis49-pore

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 yuni-lapis49-pore package and monitor your project for any dependencies that may have been affected by this malicious code. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities without needing to access the code directly.

Conclusion

The yuni-lapis49-pore package presents a significant threat to the npm ecosystem due to its malicious behavior. Developers are advised to remove this package and monitor their dependencies closely. Utilizing tools like Vulert can help in maintaining the security of your projects.

See every vulnerability recorded for yuni-lapis49-pore →

Share this vulnerability

FAQ

yuni-lapis49-pore is an npm package involved in a malicious campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project if you inadvertently use affected packages.

You should uninstall the package immediately and review your project's dependencies for any potential vulnerabilities.

Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code.

You can use the Vulert playground to check if your application is affected by this vulnerability without signing up.

How To Fix

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

npm uninstall yuni-lapis49-pore

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