Critical Malicious Code Vulnerability in @rsgweb/utils Package

@rsgweb/utils Updated 06 Feb 2026

Summary

06/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-801: Malicious code in @rsgweb/utils (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 @rsgweb/utils package is a utility library designed for use in JavaScript applications, particularly within the npm ecosystem. It provides various functions and tools that developers can leverage to enhance their applications. However, this package has been compromised, leading to significant security concerns due to embedded malicious code.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @rsgweb/utils package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has embedded harmful code into the package, which poses a severe risk to users and their systems.

How To Fix

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

npm uninstall @rsgweb/utils

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package and securing your system.

Conclusion

The @rsgweb/utils package has been compromised with malicious code, posing a significant risk to users. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities is essential to maintain the security of your applications.

See every vulnerability recorded for @rsgweb/utils →

Share this vulnerability

FAQ

You should immediately remove the package and rotate any sensitive information stored on your system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the package-lock.json file.

After removing the package, ensure to rotate all secrets and keys stored on the affected machine and monitor for any unusual activity.

How To Fix

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

npm uninstall @rsgweb/utils

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