Malicious Code Vulnerability in cookie-mapper: A Threat to npm Users

cookie-mapper Updated 23 Dec 2025

Summary

23/12/2025
CRITICAL
No i
Critical
Not published

MAL-2025-192728: Malicious code in cookie-mapper (npm). Affects cookie-mapper versions 1.1.0. 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

cookie-mapper is an npm package designed to facilitate the mapping of cookies in web applications. It is commonly used by developers to manage cookie data efficiently. However, this package has been identified as containing malicious code, which poses significant risks to users who rely on it for secure cookie management.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the cookie-mapper package, specifically in version 1.1.0. This code can potentially compromise user data, allowing attackers to manipulate cookie information or execute unauthorized actions within applications that utilize this package. The malicious code was identified by ReversingLabs and is documented in the Open Source Vulnerability database.

How To Fix

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

npm uninstall cookie-mapper

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 cookie-mapper package from their project until a secure version is released. This can be done with the following command: npm uninstall cookie-mapper. Consider using alternative packages that provide similar functionality without the associated risks.

Conclusion

The discovery of malicious code in the cookie-mapper package highlights the importance of vigilance in managing dependencies in software projects. Users are urged to update or remove the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for cookie-mapper →

Share this vulnerability

FAQ

The malicious code can manipulate cookie data and potentially allow unauthorized access to user sessions.

You can use Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If an immediate update is not possible, consider removing the package and using an alternative until a secure version is available.

The vulnerability was discovered by ReversingLabs, which specializes in identifying malicious packages in open-source ecosystems.

Currently, version 1.1.0 is known to be affected. Always check the package repository for updates on other potentially affected versions.

How To Fix

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

npm uninstall cookie-mapper

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