Malicious Code Injection in piluvaika-kaiu-nubi Package

piluvaika-kaiu-nubi Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164260: Malicious code in piluvaika-kaiu-nubi (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The piluvaika-kaiu-nubi package is part of the npm ecosystem, often utilized for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. This package, like others in the campaign, is designed to inflate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the piluvaika-kaiu-nubi package stems from malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, which leads to the continuous republishing of these variants. The origin of this issue is linked to the tea.xyz token reward campaign, which employs these tactics to manipulate npm registry metrics. The ramifications include potential security risks for applications using this package, as it can lead to unintended exposure of sensitive data and compromise the integrity of the software.

How To Fix

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

npm uninstall piluvaika-kaiu-nubi

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 piluvaika-kaiu-nubi package altogether and look for alternative packages that provide similar functionality without the associated risks.

Conclusion

The piluvaika-kaiu-nubi package contains malicious code that poses significant risks to applications using it. Immediate action is required to uninstall the package and seek alternatives. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for piluvaika-kaiu-nubi →

Share this vulnerability

FAQ

The piluvaika-kaiu-nubi package is an npm package linked to the tea.xyz token reward campaign, which has been identified as containing malicious code.

The malicious code modifies your package.json file, potentially exposing your application to security vulnerabilities and affecting its integrity.

You should uninstall the piluvaika-kaiu-nubi package immediately using the command: npm uninstall piluvaika-kaiu-nubi.

Yes, consider looking for other npm packages that provide similar functionalities without the risk of malicious code.

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

How To Fix

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

npm uninstall piluvaika-kaiu-nubi

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