Critical Malicious Code Vulnerability in consolelofy Package

consolelofy Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1195: Malicious code in consolelofy (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The consolelofy package is an npm module designed for enhancing console logging in JavaScript applications. It provides developers with tools to format and manage console output more effectively. However, this package has been identified as containing malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the consolelofy package. This code can fully compromise any computer that has the package installed or running, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has embedded harmful code in the package, which can lead to severe security breaches and potential data loss.

How To Fix

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

npm uninstall consolelofy

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 workaround, it is recommended to avoid using the consolelofy package altogether and look for alternative packages that provide similar functionality without the associated risks. Always ensure to review the security status of any package before installation.

Conclusion

The consolelofy package has been identified as a significant security risk due to the presence of malicious code. Immediate action is required to remove the package and secure any sensitive information. Always be vigilant about the packages you use in your projects and consider using tools like Vulert to monitor for vulnerabilities.

See every vulnerability recorded for consolelofy →

Share this vulnerability

FAQ

consolelofy is an npm package designed to enhance console logging in JavaScript applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately uninstall the consolelofy package and rotate any sensitive information stored on your system.

Yes, consider using other logging packages that do not have known vulnerabilities. Always check the security status of packages before use.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

How To Fix

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

npm uninstall consolelofy

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