Malicious Code Injection in piluka-ali-ipib: A Threat to npm Users

piluka-ali-ipib Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164226: Malicious code in piluka-ali-ipib (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'piluka-ali-ipib' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit npm's publishing system. It is designed to automatically generate and publish derivative packages with altered metadata, which can mislead developers and inflate reputation scores for token rewards.

Vulnerability Detail

The vulnerability in 'piluka-ali-ipib' originates from its involvement in the tea.xyz token reward campaign. The package contains scripts that modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the integrity of the ecosystem. The malicious payload can affect developers by introducing untrusted code into their projects, leading to security risks and loss of control over their dependencies.

How To Fix

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

npm uninstall piluka-ali-ipib

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 'piluka-ali-ipib' package and any other packages that may be part of the malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and address vulnerabilities.

Conclusion

The 'piluka-ali-ipib' package poses a significant risk to npm users due to its malicious behavior. It is crucial to take immediate action by removing this package and monitoring your project for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for piluka-ali-ipib →

Share this vulnerability

FAQ

The 'piluka-ali-ipib' package is an npm package that has been identified as part of a malicious campaign aimed at exploiting the npm registry.

This vulnerability can introduce untrusted code into your project, potentially compromising its security and integrity.

You should uninstall the 'piluka-ali-ipib' package immediately and check your project for any other affected packages.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. You can also check your application using the Vulert playground without signup.

Regularly audit your dependencies, keep your packages updated, and use tools that monitor for vulnerabilities to help prevent such issues.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall piluka-ali-ipib

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