Malicious Code Vulnerability in rce-pkg-1: npm Package Compromise

rce-pkg-1 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1833: Malicious code in rce-pkg-1 (npm). Affects rce-pkg-1 versions 1.0.0 – 1.1.0. 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

rce-pkg-1 is an npm package designed for remote code execution functionalities. It is utilized in various applications to facilitate remote operations. However, this package has been identified to contain malicious code that could compromise the security of applications using it, making it a significant risk for developers and users alike.

Vulnerability Detail

The vulnerability in rce-pkg-1 stems from the inclusion of malicious code that can execute unauthorized commands on the host machine. This issue was reported by ReversingLabs and affects versions 1.0.0 and 1.1.0. The malicious code can lead to data breaches, unauthorized access, and potential control over the affected systems, posing severe risks to application integrity and user data.

How To Fix

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

npm uninstall rce-pkg-1

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 rce-pkg-1 package from your project until a secure version is released. You can do this by running the command: npm uninstall rce-pkg-1. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The rce-pkg-1 npm package has been identified with a serious vulnerability due to malicious code that can compromise application security. It is crucial for developers to update or remove this package to protect their applications and users from potential threats.

See every vulnerability recorded for rce-pkg-1 →

Share this vulnerability

FAQ

rce-pkg-1 is an npm package that facilitates remote code execution functionalities in applications.

The malicious code can execute unauthorized commands, leading to data breaches and unauthorized access to your system.

Versions 1.0.0 and 1.1.0 of rce-pkg-1 are known to contain the malicious code.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

If an immediate update is not possible, consider removing the package and using alternative solutions until a secure version is available.

How To Fix

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

npm uninstall rce-pkg-1

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