Critical Malicious Code Vulnerability in researchpoc2 Package

researchpoc2 Updated 29 Jan 2026

Summary

29/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-600: Malicious code in researchpoc2 (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The researchpoc2 package is a Node.js library available through npm, designed for research purposes. It is often utilized by developers to facilitate various functionalities in their applications. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the researchpoc2 package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it can lead to data breaches and loss of control over the affected systems. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code.

How To Fix

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

npm uninstall researchpoc2

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 are no effective workarounds for this vulnerability other than removing the package and securing your system. It is essential to monitor your system for any signs of compromise after the removal.

Conclusion

The researchpoc2 package has been identified as containing malicious code that can compromise systems. Immediate action is required to uninstall the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for researchpoc2 →

Share this vulnerability

FAQ

Immediately uninstall the package using npm uninstall researchpoc2 and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Leaving the package installed can lead to unauthorized access to your system, data breaches, and potential control loss over your applications and sensitive information.

No, there is currently no patched version available for the researchpoc2 package. The only solution is to uninstall it.

Regularly monitor your dependencies using tools like Vulert, and ensure to keep your packages updated. Always review package sources and community feedback before installation.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall researchpoc2

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