Malicious Code Injection in pilka-kali-nuliva: A Threat to npm Packages

pilka-kali-nuliva Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164122: Malicious code in pilka-kali-nuliva (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 'pilka-kali-nuliva' is part of a broader campaign targeting npm, designed to exploit the npm registry by flooding it with malicious packages. These packages are often linked to token reward schemes, which incentivize developers to publish numerous packages, thereby inflating their reputation scores. The malicious nature of 'pilka-kali-nuliva' lies in its ability to modify package metadata and continuously republish variants, posing a significant risk to developers and users relying on npm for package management.

Vulnerability Detail

The vulnerability in 'pilka-kali-nuliva' originates from its association with the tea.xyz token reward campaign. It employs scripts that alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the pollution of the npm registry, making it difficult for developers to find legitimate packages and potentially introducing security risks into their applications.

How To Fix

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

npm uninstall pilka-kali-nuliva

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, avoid using 'pilka-kali-nuliva' and any other packages associated with the tea.xyz campaign. Monitor your package.json and package-lock.json files for any unauthorized changes, and consider using tools like Vulert to track vulnerabilities in your dependencies.

Conclusion

The 'pilka-kali-nuliva' package poses a significant threat to npm users due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package and monitor your dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for pilka-kali-nuliva →

Share this vulnerability

FAQ

'pilka-kali-nuliva' is an npm package that has been identified as malicious, part of a campaign to manipulate the npm registry.

The vulnerability can lead to the introduction of malicious code into your application, compromising its security and integrity.

You should uninstall the package immediately using 'npm uninstall pilka-kali-nuliva' and review your project for any other affected dependencies.

You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access or installation.

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 pilka-kali-nuliva

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