Critical Malicious Code Vulnerability in cookie-loggo Package

cookie-loggo Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6360: Malicious code in cookie-loggo (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The cookie-loggo package is a Node.js library designed for logging cookie data in web applications. It provides developers with a simple interface to track and manage cookies, enhancing debugging and monitoring capabilities. However, this package has been identified to contain malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the cookie-loggo package. This code can lead to full compromise of the affected system, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code poses significant risks, as it may enable attackers to control the system remotely and exploit it for various malicious activities.

How To Fix

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

npm uninstall cookie-loggo

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

Currently, there are no effective workarounds to mitigate the risks posed by the cookie-loggo package. The only safe course of action is to uninstall the package and secure the system.

Conclusion

The cookie-loggo package contains embedded malicious code that poses a severe security risk to any system it is installed on. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities using tools like Vulert can help prevent such issues in the future.

See every vulnerability recorded for cookie-loggo →

Share this vulnerability

FAQ

cookie-loggo is a Node.js library used for logging cookie data in web applications.

The malicious code can lead to full system compromise, allowing unauthorized access to sensitive information and potential remote control by attackers.

You should immediately uninstall the cookie-loggo package and rotate all sensitive information stored on the affected system.

As of now, there is no patched version available. The best course of action is to remove the package entirely.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without requiring access to the code or installation.

How To Fix

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

npm uninstall cookie-loggo

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