Critical Malicious Code Vulnerability in rtxnode-sass22 Package

rtxnode-sass22 Updated 10 Mar 2026

Summary

10/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1322: Malicious code in rtxnode-sass22 (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 rtxnode-sass22 package is an npm library that is typically used for compiling Sass stylesheets into CSS. It is designed to streamline the development process by allowing developers to write styles in Sass, which is then converted into standard CSS for use in web applications. However, this package has been identified to contain malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the rtxnode-sass22 package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to a complete takeover of the affected system by external entities. Users are advised to treat any system with this package installed as fully compromised.

How To Fix

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

npm uninstall rtxnode-sass22

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

There are no effective workarounds for this vulnerability other than removing the package entirely. Ensure that you have backups of your work and consider using alternative packages that do not pose security risks.

Conclusion

The rtxnode-sass22 package has been identified as containing malicious code, which poses a significant security threat to any system using it. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is crucial to maintaining a secure development environment.

See every vulnerability recorded for rtxnode-sass22 →

Share this vulnerability

FAQ

You should uninstall the rtxnode-sass22 package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Leaving this package installed can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

The only effective mitigation is to uninstall the package and use alternative libraries that do not contain malicious code.

While many npm packages are safe, it's essential to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall rtxnode-sass22

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