Malicious Code Injection in patria-rendang83-remi Package

patria-rendang83-remi Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-106974: Malicious code in patria-rendang83-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 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 patria-rendang83-remi package is part of a broader ecosystem within npm, often associated with token reward campaigns. These packages are designed to manipulate npm's package registry by generating and publishing numerous derivative packages with randomized names. This behavior is primarily aimed at inflating developer reputation scores for rewards associated with the tea protocol.

Vulnerability Detail

The vulnerability in the patria-rendang83-remi package stems from its malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and creates random package names, leading to the continuous republishing of these variants. The origin of this issue is linked to a campaign that floods the npm registry with such packages, which can severely compromise the integrity of the registry and potentially affect developers relying on these packages.

How To Fix

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

npm uninstall patria-rendang83-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 workaround, you can avoid using the patria-rendang83-remi package altogether. If you have dependencies relying on it, consider finding alternative packages that do not exhibit malicious behavior.

Conclusion

The patria-rendang83-remi package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to remove this package from your projects and monitor for similar vulnerabilities using tools like Vulert.

See every vulnerability recorded for patria-rendang83-remi →

Share this vulnerability

FAQ

It is a malicious npm package associated with a token reward campaign that manipulates the npm registry.

It can lead to the pollution of the npm registry and potentially compromise the integrity of your project's dependencies.

You should uninstall the package immediately using 'npm uninstall patria-rendang83-remi' to mitigate any risks.

No, the package is identified as malicious and should not be used. There are no patches available.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall patria-rendang83-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