Critical Malicious Code Vulnerability in researchpoc Package

researchpoc Updated 06 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-662: Malicious code in researchpoc (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The researchpoc package is an npm library designed for research purposes, often utilized in various JavaScript applications. It allows developers to prototype and test concepts quickly. However, this package has been identified to contain malicious code that compromises the security of systems where it is installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the researchpoc package. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code poses significant risks, as it may not only affect the immediate application but also extend to the entire system, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall researchpoc

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, if immediate removal is not feasible, consider isolating the application using containerization or virtual environments to limit the impact of the malicious code until a proper fix can be applied.

Conclusion

The researchpoc package has been identified as containing malicious code that poses significant security risks. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for researchpoc →

Share this vulnerability

FAQ

researchpoc is an npm package used for research and prototyping in JavaScript applications.

The malicious code can lead to unauthorized access to sensitive information and may compromise the entire system.

You should immediately remove the researchpoc package and rotate any secrets or keys stored on your system.

Yes, you can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

Failing to address this vulnerability can lead to data breaches, unauthorized access, and potential loss of sensitive information.

Related vulnerabilities

Recent vulnerabilities recorded for researchpoc.

How To Fix

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

npm uninstall researchpoc

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