Malicious Code Injection in poli-aki-alub Package - npm Vulnerability

poli-aki-alub Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-164343: Malicious code in poli-aki-alub (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 poli-aki-alub 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 the npm registry by flooding it with derivative packages. The primary functionality of this package is to serve as a token reward mechanism for the tea.xyz protocol, but it has been compromised to include harmful scripts that manipulate package metadata.

Vulnerability Detail

The vulnerability in the poli-aki-alub package originates from its association with a malicious campaign that generates and publishes numerous derivative packages with randomized names. These packages contain scripts that modify the package.json file to remove private flags, alter version numbers, and continuously republish variants, thereby polluting the npm registry. This can lead to significant security risks, including the potential for unauthorized access to sensitive data and the degradation of the npm ecosystem's integrity.

How To Fix

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

npm uninstall poli-aki-alub

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 prevent the installation of the poli-aki-alub package by adding it to your project's .npmrc file with the following line: 'package-lock=false'. This will stop npm from installing this package until a fix is applied.

Conclusion

The poli-aki-alub package has been identified as a malicious entity within the npm ecosystem, posing significant risks to projects that utilize it. Immediate action is required to remove this package and safeguard your application from potential threats. Utilizing tools like Vulert can help maintain the security of your open-source dependencies.

See every vulnerability recorded for poli-aki-alub →

Share this vulnerability

FAQ

The poli-aki-alub package is an npm package that is part of a token reward campaign but has been identified as malicious due to its harmful scripts.

This vulnerability can compromise your project's security by allowing unauthorized access to sensitive data and polluting the npm registry with malicious packages.

You should uninstall the poli-aki-alub package immediately using 'npm uninstall poli-aki-alub' and check your package-lock.json for any references.

Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can check for vulnerabilities without any signup at the Vulert playground.

Regularly audit your dependencies using tools like npm audit and consider using Vulert to monitor your projects for vulnerabilities.

How To Fix

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

npm uninstall poli-aki-alub

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