Malicious Code Detected in generic-rpc Package - Immediate Action Required

generic-rpc Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21315: Malicious code in generic-rpc (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 generic-rpc package is a Node.js library designed to facilitate remote procedure calls in a generic manner. It allows developers to create and manage RPCs easily, making it a popular choice for building distributed applications. However, this package has been found to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the generic-rpc package stems from the inclusion of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to mitigate potential risks.

How To Fix

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

npm uninstall generic-rpc

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 generic-rpc package from your project if it is not essential. This can be done using the command: npm uninstall generic-rpc. Alternatively, consider using a different library that provides similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the generic-rpc package presents a serious threat to applications that utilize it. Users must take prompt action to update or remove the package to safeguard their systems. Utilizing tools like Vulert can help monitor for such vulnerabilities effectively.

See every vulnerability recorded for generic-rpc →

Share this vulnerability

FAQ

The generic-rpc package is a Node.js library that simplifies the creation and management of remote procedure calls in distributed applications.

The malicious code can lead to unauthorized access and potential data breaches, posing significant security risks to applications using the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without any signup.

Yes, users are advised to update to the latest patched version of the generic-rpc package to mitigate the vulnerability.

If an immediate update is not possible, consider removing the package or replacing it with a safer alternative until a patch can be applied.

How To Fix

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

npm uninstall generic-rpc

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