Malicious Code Injection in patria-jengkol32-apidev Package

patria-jengkol32-apidev Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-89391: Malicious code in patria-jengkol32-apidev (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 patria-jengkol32-apidev package is part of the npm ecosystem, typically used for developing applications that may involve API interactions. This package has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The vulnerability stems from its design to modify critical files and republish variants, leading to potential security risks for developers using it.

Vulnerability Detail

The vulnerability in the patria-jengkol32-apidev package originates from its association with the tea.xyz token reward campaign. It contains scripts that automatically modify the package.json file, removing private flags and altering version numbers. This behavior allows the package to generate random names and continuously republish itself, polluting the npm registry. The ramifications include compromised package integrity, potential exposure of sensitive data, and a degraded developer reputation due to the proliferation of malicious packages.

How To Fix

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

npm uninstall patria-jengkol32-apidev

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 package from executing its malicious scripts by using the following command to uninstall it: npm uninstall patria-jengkol32-apidev. Additionally, ensure that your package.json file is reviewed for any unauthorized changes.

Conclusion

The patria-jengkol32-apidev package has been compromised with malicious code that alters critical files and repopulates itself in the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities effectively.

See every vulnerability recorded for patria-jengkol32-apidev →

Share this vulnerability

FAQ

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

The vulnerability can lead to unauthorized modifications of your package.json file and the proliferation of malicious packages in your project.

You should update the package to a patched version or uninstall it to mitigate the risk.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time.

Yes, you can use the Vulert playground at Vulert Scanner to check 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 patria-jengkol32-apidev

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