Malicious Code Injection in Vointea Package: npm Vulnerability Overview

vointea Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91982: Malicious code in vointea (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

Vointea is an npm package that is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious packages flooding the npm registry. These packages are designed to manipulate developer reputation scores through automated publishing scripts. The functionality of Vointea is compromised due to its involvement in this campaign, making it a target for developers who may unknowingly install it.

Vulnerability Detail

The vulnerability in the Vointea package stems from its malicious code that modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior not only affects the integrity of the npm ecosystem but also poses risks to developers who may inadvertently install these compromised packages, leading to potential security breaches in their applications.

How To Fix

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

npm uninstall vointea

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 Vointea package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for vulnerabilities using tools like Vulert.

Conclusion

The Vointea package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. Developers should take immediate action to remove this package and utilize tools like Vulert to monitor their projects for vulnerabilities. Awareness and proactive measures are essential to maintaining the security of software applications.

See every vulnerability recorded for vointea →

Share this vulnerability

FAQ

Vointea is an npm package that is part of a campaign to inflate developer reputation scores through the publication of malicious packages.

The vulnerability can lead to the installation of malicious code that compromises your application's integrity and security.

You should uninstall the Vointea package immediately and check your project for any unintended consequences of its installation.

You can use tools like Vulert to monitor your package-lock.json file for real-time alerts on open-source vulnerabilities.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.

How To Fix

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

npm uninstall vointea

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