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

victim-package-c Updated 21 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

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

victim-package-c is an npm package that serves as a utility for developers, providing various functionalities to enhance application development. However, it has been identified as containing malicious code, which poses significant security risks to any system utilizing this package. The vulnerability allows attackers to gain unauthorized access and control over affected systems, compromising sensitive data and secrets.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the victim-package-c package. This code can fully compromise any computer that has the package installed or running. Attackers can potentially access all secrets and keys stored on the compromised system. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code. Users are advised to treat any system with this package as fully compromised.

How To Fix

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

npm uninstall victim-package-c

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package and rotating all secrets and keys stored on the affected system.

Conclusion

The discovery of malicious code within the victim-package-c npm package poses a serious threat to users and their systems. Immediate action is required to remove the package and secure any compromised data. Utilizing tools like Vulert can aid in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for victim-package-c →

Share this vulnerability

FAQ

Immediately remove the victim-package-c package from your system and rotate all secrets and keys stored on that computer.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Failure to address this vulnerability can lead to unauthorized access to sensitive data, complete control of your system by attackers, and potential data breaches.

As of now, there is no patch available. The recommended action is to remove the package entirely.

Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing an efficient way to stay informed about potential risks.

How To Fix

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

npm uninstall victim-package-c

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