Malicious Code Injection in putri-rangginang78-remi Package

putri-rangginang78-remi Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107531: Malicious code in putri-rangginang78-remi (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The putri-rangginang78-remi package is part of a larger ecosystem within the npm registry, often associated with token reward campaigns. It is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores. This package, like others in its category, is vulnerable to exploitation due to its inherent design that allows for the modification of critical files such as package.json.

Vulnerability Detail

The vulnerability originates from the malicious code embedded within the putri-rangginang78-remi package. This code is designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names that are often Indonesian-themed. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to reputation damage for developers and security risks for users who unknowingly install these compromised packages.

How To Fix

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

npm uninstall putri-rangginang78-remi

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 putri-rangginang78-remi package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can use tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.

Conclusion

The putri-rangginang78-remi package poses significant risks due to its embedded malicious code. It is crucial for developers to be vigilant about the packages they use and to employ tools like Vulert for ongoing monitoring. By following the recommended steps to remove the package and staying informed about updates, developers can protect their projects from potential threats.

See every vulnerability recorded for putri-rangginang78-remi →

Share this vulnerability

FAQ

It is an npm package associated with token reward campaigns that generates and publishes derivative packages.

The malicious code modifies critical files, potentially leading to security vulnerabilities and reputation damage.

You should uninstall the package immediately and monitor your project for any other vulnerabilities.

Yes, regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities in real-time.

You can use the Vulert playground at Vulert Scanner to check your application for vulnerabilities without needing to sign up.

How To Fix

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

npm uninstall putri-rangginang78-remi

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