CVE-2022-5622: Malicious code in rdocumentation-workers (npm)

rdocumentation-workers Updated 02 Oct 2025

Summary

31/10/2022
CRITICAL
No i
Critical
Not published

MAL-2022-5622: Malicious code in rdocumentation-workers (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rdocumentation-workers package is an npm package that provides functionality for generating documentation for R packages. It is commonly used in projects that involve R programming language. The package is vulnerable to a malicious code injection attack, which can compromise the security of any computer that has the package installed or running.

Vulnerability Detail

The vulnerability originates from a malicious code injection in the rdocumentation-workers package. Any computer with the package installed or running should be considered fully compromised. This means that all secrets and keys stored on that computer should be rotated immediately from a different computer. Simply removing the package may not remove all the malicious software installed as a result of the attack.

How To Fix

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

npm uninstall rdocumentation-workers

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 is no specific workaround mentioned for this vulnerability. However, it is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The rdocumentation-workers package is vulnerable to a malicious code injection attack, which can compromise the security of any computer that has the package installed or running. It is crucial to follow the recommended steps to mitigate the risk and ensure the security of your system. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for rdocumentation-workers →

Share this vulnerability

FAQ

The impact of this vulnerability is severe as it compromises the security of the affected computer and exposes all stored secrets and keys to potential misuse.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your computer is affected by this vulnerability. It analyzes the package-lock.json file to identify vulnerabilities in your software.

Removing the rdocumentation-workers package is recommended, but it may not remove all the malicious software installed as a result of the attack. It is crucial to rotate all secrets and keys stored on the compromised computer from a different computer.

It is recommended to search for alternative packages that provide similar functionality and have a good security track record. Conduct thorough research and consider community recommendations before adopting a new package.

To prevent similar vulnerabilities in the future, it is important to regularly update packages to their latest versions, follow security best practices, and use tools like Vulert to monitor and alert for open-source vulnerabilities in your software.

How To Fix

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

npm uninstall rdocumentation-workers

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