Malicious Code Injection in vera-gaplek25-riris Package - npm Vulnerability

vera-gaplek25-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-91681: Malicious code in vera-gaplek25-riris (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The vera-gaplek25-riris package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been identified as containing malicious code that compromises its integrity and the security of the npm registry.

Vulnerability Detail

The vulnerability originates from the malicious intent behind the vera-gaplek25-riris package, which is designed to automatically modify package.json files to remove private flags, alter version numbers, and generate random package names. This behavior leads to the pollution of the npm registry and can inflate developer reputation scores fraudulently. The malicious payload can potentially affect other packages and users relying on the npm ecosystem, leading to security risks and trust issues within the community.

How To Fix

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

npm uninstall vera-gaplek25-riris

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 vera-gaplek25-riris package and monitor your package-lock.json file for any unauthorized changes. Regularly audit your dependencies using tools like npm audit to identify and mitigate vulnerabilities.

Conclusion

The vera-gaplek25-riris package poses a significant security risk due to its malicious code that alters package files and inflates developer reputation scores. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.

See every vulnerability recorded for vera-gaplek25-riris →

Share this vulnerability

FAQ

The vera-gaplek25-riris package is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies package.json files, removes private flags, and generates random package names, which can lead to security risks and pollution of the npm registry.

If you have installed the vera-gaplek25-riris package, it is recommended to remove it immediately and audit your project for any unauthorized changes.

Yes, you can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall vera-gaplek25-riris

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