Malicious Code Injection in joko-sate54-remi Package - npm Vulnerability

joko-sate54-remi Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104644: Malicious code in joko-sate54-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 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 joko-sate54-remi package is part of the npm ecosystem, often utilized in JavaScript projects for various functionalities. However, it has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, which can lead to significant security risks for users.

Vulnerability Detail

The vulnerability originates from the malicious code embedded in the joko-sate54-remi package. This code modifies the package.json file to remove private flags, alters version numbers, and generates random package names, contributing to the pollution of the npm registry. The ramifications include potential exposure of sensitive data, unauthorized access to systems, and the proliferation of malicious packages that can compromise the integrity of software projects.

How To Fix

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

npm uninstall joko-sate54-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 remove the joko-sate54-remi package from your project by executing the following command: npm uninstall joko-sate54-remi. This will prevent any malicious code from executing in your application.

Conclusion

The joko-sate54-remi package poses a significant security risk due to its embedded malicious code. Users are encouraged to update or remove the package to safeguard their projects. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in real-time.

See every vulnerability recorded for joko-sate54-remi →

Share this vulnerability

FAQ

The package contains malicious code that modifies project files and floods the npm registry with derivative packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

If no patched version is available, it is advisable to remove the package from your project to mitigate the risk.

The malicious code can lead to unauthorized access, data exposure, and the introduction of additional vulnerabilities through the proliferation of derivative packages.

Regularly audit your dependencies, use tools like Vulert for monitoring, and ensure that you only use trusted packages from reputable sources.

How To Fix

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

npm uninstall joko-sate54-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