Malicious Code Detected in ranko887: A Critical npm Vulnerability

ranko887 Updated 19 Mar 2026

Summary

18/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1832: Malicious code in ranko887 (npm). Affects ranko887 versions 1.0.0 – 1.0.4. 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

ranko887 is an npm package designed for [insert functionality here, e.g., 'data processing', 'web development', etc.]. It is widely used in various projects due to its [insert key attributes, e.g., 'ease of use', 'performance', etc.]. However, recent findings have revealed that this package is susceptible to malicious code injections, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in ranko887 stems from the introduction of malicious code within its versions 1.0.0, 1.0.1, and 1.0.4. This code can lead to unauthorized access, data breaches, or other harmful actions within the host application. The malicious nature of the code was identified by ReversingLabs, highlighting the importance of scrutinizing third-party packages for security risks.

How To Fix

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

npm uninstall ranko887

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 temporary workaround, consider removing the ranko887 package from your project until a secure version is released. You can do this by running: npm uninstall ranko887.

Conclusion

The discovery of malicious code in the ranko887 npm package underscores the importance of vigilance when using third-party libraries. Users are encouraged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for ranko887 →

Share this vulnerability

FAQ

ranko887 is an npm package used for [insert functionality here].

Versions 1.0.0, 1.0.1, and 1.0.4 of ranko887 are known to contain malicious code.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities. Simply upload your package-lock.json file to the Vulert playground at Vulert Scanner to check for vulnerabilities.

The vulnerability was identified by ReversingLabs, a security research firm specializing in malware analysis.

If immediate updates are not feasible, consider removing the package from your project as a temporary measure until a secure version is available.

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 ranko887

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