CVE-2022-2923: Malicious code in exporting-ref-project (npm)

exporting-ref-project Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-2923: Malicious code in exporting-ref-project (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 exporting-ref-project is an npm package used for exporting reference projects. It provides functionality for exporting project files and configurations. 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 specific version of the exporting-ref-project package (0.0.0). This version contains malicious code that can give full control of the affected computer to an outside entity. As a result, all secrets and keys stored on the compromised computer should be rotated immediately from a different computer. Simply removing the package may not guarantee the removal of all malicious software installed as a result of its installation.

How To Fix

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

npm uninstall exporting-ref-project

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. The recommended course of action is to follow the steps mentioned in the 'how_to_fix' section.

Conclusion

The exporting-ref-project package is vulnerable to a malicious code injection attack, which can compromise the security of the affected computer. It is crucial to remove the package, rotate all secrets and keys, and scan for any remaining traces of malicious software. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for exporting-ref-project →

Share this vulnerability

FAQ

The exporting-ref-project is an npm package used for exporting reference projects. It provides functionality for exporting project files and configurations.

The vulnerability can compromise the security of any computer that has the exporting-ref-project package installed or running. It can give full control of the affected computer to an outside entity, potentially exposing sensitive information and allowing unauthorized access.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes the package-lock.json file and alerts in real-time for open-source vulnerabilities.

If your computer is affected, it is recommended to remove the exporting-ref-project package, rotate all secrets and keys stored on the compromised computer from a different, secure computer, and scan for any remaining traces of malicious software.

Yes, the fix for this vulnerability is to remove the exporting-ref-project package and take appropriate actions to secure the compromised computer.

How To Fix

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

npm uninstall exporting-ref-project

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