Malicious Code Injection in nana-kripik91-riris Package

nana-kripik91-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-88685: Malicious code in nana-kripik91-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 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 nana-kripik91-riris package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and the security of applications that depend on it.

Vulnerability Detail

The vulnerability in the nana-kripik91-riris package originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially affecting other packages and applications that rely on npm. The malicious scripts included in this package are designed to automate the process of creating and publishing these harmful derivatives, posing a significant risk to developers and users alike.

How To Fix

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

npm uninstall nana-kripik91-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 prevent the installation of this package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not include this package in your project and regularly audit your dependencies for any malicious packages.

Conclusion

The nana-kripik91-riris package poses a significant security risk due to its malicious code that alters package metadata and floods the npm registry with harmful derivatives. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity and security of their applications.

See every vulnerability recorded for nana-kripik91-riris →

Share this vulnerability

FAQ

The nana-kripik91-riris package is an npm package involved in the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The malicious code modifies your package.json file, removes private flags, and can lead to the pollution of the npm registry, affecting other packages and applications.

You should uninstall the nana-kripik91-riris package immediately and check your project for any references to it in your package-lock.json file.

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

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

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 nana-kripik91-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