Malicious Code Detected in blimps Package - Security Alert

blimps Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15816: Malicious code in blimps (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

The blimps package is an npm library designed for managing and manipulating data structures in a lightweight manner. It is often used in applications that require efficient data handling. However, recent findings have revealed that this package contains malicious code, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the blimps package originates from the inclusion of malicious code that can compromise the integrity of applications using it. This code may lead to unauthorized access, data breaches, or other harmful actions within the user's environment. The malicious nature of this code can severely impact application security and user trust.

How To Fix

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

npm uninstall blimps

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, users can remove the blimps package from their project until a secure version is released. This can be done using the command: npm uninstall blimps.

Conclusion

The discovery of malicious code in the blimps package highlights the importance of regularly monitoring and updating open-source dependencies. Users are advised to take immediate action to secure their applications by updating or removing the affected package.

See every vulnerability recorded for blimps →

Share this vulnerability

FAQ

The blimps package is used for managing and manipulating data structures in a lightweight manner within JavaScript applications.

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 any signup.

If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks associated with the malicious code.

As of now, users should check the official npm repository for any updates or patches related to the blimps package.

Using the compromised blimps package can lead to unauthorized access, data breaches, and other security vulnerabilities that can harm your application and its users.

How To Fix

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

npm uninstall blimps

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