Critical Malicious Code Vulnerability in victim-package-b (npm)

victim-package-b Updated 21 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-400: Malicious code in victim-package-b (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

victim-package-b is an npm package commonly used for various functionalities in JavaScript applications. It is designed to provide developers with tools and libraries to enhance their projects. However, this package has been compromised, leading to a serious security vulnerability that can fully compromise any system where it is installed.

Vulnerability Detail

The vulnerability originates from the presence of malicious code embedded within the victim-package-b package. This code can grant unauthorized access to the system, allowing attackers to exploit sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as any computer running this package should be considered fully compromised, necessitating immediate action to secure the system.

How To Fix

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

npm uninstall victim-package-b

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

As a workaround, it is recommended to rotate all secrets and keys stored on the compromised computer from a different, secure machine. This step is essential to mitigate the risks associated with the malicious code.

Conclusion

The discovery of malicious code in the victim-package-b npm package poses a significant threat to any system using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Users are encouraged to utilize tools like Vulert for ongoing monitoring of their dependencies.

See every vulnerability recorded for victim-package-b →

Share this vulnerability

FAQ

victim-package-b is an npm package used in JavaScript applications that has been found to contain malicious code.

If you have installed victim-package-b, your system may be compromised. It is advisable to take immediate action to secure your environment.

You should rotate all secrets and keys from a different, secure machine to prevent unauthorized access.

Currently, there is no patch available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall victim-package-b

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