CVE-2022-7004: Malicious code in vulncode-db (npm)

vulncode-db Updated 02 Oct 2025

Summary

20/06/2022
CRITICAL
No i
Critical
Not published

MAL-2022-7004: Malicious code in vulncode-db (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The vulncode-db package is an npm package that provides a database of known vulnerabilities in various software packages. It is commonly used by developers and security professionals to identify and mitigate potential security risks in their applications. However, the package itself has been compromised and contains malicious code that can fully compromise any computer on which it is installed or running. This means that all secrets and keys stored on the affected computer should be rotated immediately from a different computer. Simply removing the package may not be sufficient, as there is no guarantee that all malicious software resulting from its installation will be removed.

Vulnerability Detail

The vulnerability in the vulncode-db package is due to the presence of embedded malicious code. This code can give full control of the affected computer to an outside entity, compromising the security of any sensitive information stored on that computer. The package should be considered fully compromised, and immediate action is required to mitigate the potential damage. The exact nature and extent of the malicious code are not specified in the provided information.

How To Fix

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

npm uninstall vulncode-db

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

No specific workaround is provided in the vulnerability details. However, it is crucial to take immediate action by rotating secrets and keys and removing the vulncode-db package to minimize the potential impact of the malicious code.

Conclusion

The vulncode-db package has been compromised and contains malicious code that can fully compromise any computer on which it is installed or running. Immediate action is required to mitigate the potential damage. Rotate all secrets and keys stored on the affected computer, remove the vulncode-db package, and conduct a thorough security audit. Implement additional security measures to enhance the overall security of your applications and systems. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for vulncode-db →

Share this vulnerability

FAQ

The vulncode-db package is an npm package that provides a database of known vulnerabilities in various software packages. It helps developers and security professionals identify and mitigate potential security risks in their applications.

The malicious code in vulncode-db can give full control of the affected computer to an outside entity. This compromises the security of any sensitive information stored on that computer.

If you have the vulncode-db package installed, it is crucial to take immediate action. Rotate all secrets and keys stored on the affected computer from a different, trusted computer, and remove the vulncode-db package. Conduct a thorough security audit to identify any potential unauthorized access or compromise.

There is no guarantee that simply removing the vulncode-db package will remove all malicious software resulting from its installation. It is recommended to conduct a thorough security audit to identify and mitigate any potential unauthorized access or compromise.

To protect against similar vulnerabilities, it is recommended to regularly update and patch software, use strong and unique passwords, and employ multi-factor authentication. These measures can help enhance the overall security of your applications and systems.

How To Fix

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

npm uninstall vulncode-db

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