Critical Malicious Code Vulnerability in geepurin Package

geepurin Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21253: Malicious code in geepurin (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 geepurin package is an npm library designed for specific functionalities within JavaScript applications. It is utilized for various purposes, including data manipulation and user interface enhancements. However, it has been identified to contain malicious code that poses significant risks to applications relying on it. This vulnerability can compromise the integrity and security of the software utilizing the package.

Vulnerability Detail

The vulnerability in the geepurin package stems from the inclusion of malicious code that can execute harmful actions within an application. This code was introduced in version 0 and can lead to unauthorized access, data breaches, or other malicious activities. The ramifications of this vulnerability are severe, as it can affect any application that incorporates the geepurin package, potentially leading to significant security incidents.

How To Fix

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

npm uninstall geepurin

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, you can avoid using the geepurin package altogether until a secure version is available. If you must use it, consider isolating its functionality and monitoring its behavior closely to mitigate potential risks.

Conclusion

The geepurin package has been identified to contain malicious code, posing significant security risks to applications that utilize it. Immediate action is required to remove the package and monitor for any updates or patches. Utilizing tools like Vulert can help in identifying vulnerabilities in your application effectively.

See every vulnerability recorded for geepurin →

Share this vulnerability

FAQ

The geepurin package is an npm library used in JavaScript applications for various functionalities, but it has been found to contain malicious code.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to use the Vulert playground without signup.

If you have installed geepurin, it is recommended to remove it immediately and check for any updates or patches that may address the vulnerability.

The risks include unauthorized access to sensitive data, potential data breaches, and the execution of harmful actions within your application.

As of now, there is no specific patch version available for the geepurin package. It is advisable to monitor the package repository for any updates.

How To Fix

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

npm uninstall geepurin

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