Critical Malicious Code Vulnerability in webpikes Package

webpikes Updated 02 Oct 2025

Summary

17/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47419: Malicious code in webpikes (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 webpikes package is a Node.js library designed for web development, providing various utilities for handling image formats and enhancing web performance. Despite its utility, the package has been found to harbor malicious code, posing significant risks to applications that utilize it. This vulnerability can compromise the integrity of applications and potentially lead to unauthorized access or data breaches.

Vulnerability Detail

The vulnerability in the webpikes package originates from the inclusion of malicious code that can execute harmful actions within the user's environment. This code can lead to data theft, unauthorized access to sensitive information, or even complete system compromise. The issue was identified in all versions starting from the initial release, indicating that any application using this package is at risk.

How To Fix

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

npm uninstall webpikes

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 replace the webpikes package with an alternative library that provides similar functionality without the associated risks. Review your project's dependencies and consider using trusted packages that are actively maintained and have a good security track record.

Conclusion

The discovery of malicious code within the webpikes package presents a serious security threat to applications that utilize it. Users are advised to remove the package and seek alternatives while keeping an eye on updates from the package maintainers. Utilizing tools like Vulert can enhance security by providing real-time monitoring for vulnerabilities.

See every vulnerability recorded for webpikes →

Share this vulnerability

FAQ

The vulnerability involves malicious code embedded within the webpikes package, which can execute harmful actions in the user's environment.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Simply upload your package-lock.json file to check for vulnerabilities.

It is recommended to remove the webpikes package from your project and replace it with a secure alternative until a patched version is released.

Currently, there is no patch available for the webpikes package. Users should monitor the package repository for any updates.

Vulert uses your package-lock.json file to monitor for vulnerabilities in your dependencies, providing real-time alerts without requiring code access or installation.

How To Fix

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

npm uninstall webpikes

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