Malicious Code Injection in putra-gaplek23-riris Package

putra-gaplek23-riris Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89556: Malicious code in putra-gaplek23-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The putra-gaplek23-riris package is part of the npm ecosystem, often used in JavaScript applications for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. This package is designed to inflate developer reputation scores through automated scripts that publish numerous variants with randomized names.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the putra-gaplek23-riris package. This code modifies the package.json file by removing private flags, altering version numbers, and generating random package names. The continuous republishing of these variants leads to pollution of the npm registry, which can affect the integrity and security of applications relying on this package. The malicious payload can compromise the developer's reputation and potentially introduce security risks into dependent applications.

How To Fix

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

npm uninstall putra-gaplek23-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 putra-gaplek23-riris package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.

Conclusion

The putra-gaplek23-riris package poses a significant risk due to its malicious code designed to manipulate package metadata and inflate developer reputation scores. It is crucial for developers to remove this package from their projects and monitor their dependencies for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for putra-gaplek23-riris →

Share this vulnerability

FAQ

It is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated publishing.

The malicious code can modify your package.json file, remove private flags, and continuously republish variants, potentially compromising your application's integrity.

You should uninstall the package immediately using 'npm uninstall putra-gaplek23-riris' and check your dependencies for any unauthorized changes.

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

Regularly audit your dependencies, keep them updated, and use tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall putra-gaplek23-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