Critical Malicious Code Vulnerability in log-symbols_updated Package

log-symbols_updated Updated 05 Feb 2026

Summary

05/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-753: Malicious code in log-symbols_updated (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 log-symbols_updated package is an npm module used for displaying log symbols in terminal applications, enhancing the readability of console output. It is commonly utilized in various Node.js applications to provide visual cues for logging. However, this package has been compromised, leading to severe security implications for any system that has it installed.

Vulnerability Detail

The vulnerability originates from the log-symbols_updated package, which contains embedded malicious code. This code can fully compromise any computer running the package, allowing unauthorized access to sensitive information such as secrets and keys. The ramifications include potential data breaches and loss of control over the affected system, as the malicious code may persist even after the package is removed.

How To Fix

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

npm uninstall log-symbols_updated

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

There are no effective workarounds for this vulnerability. The only recommended action is to remove the package entirely and secure your system.

Conclusion

The log-symbols_updated package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for log-symbols_updated →

Share this vulnerability

FAQ

You should remove the log-symbols_updated package immediately and rotate any secrets or keys stored on the affected system.

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

While removing the package is essential, you should also rotate all sensitive information and assess your system for any lingering malicious software.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your system.

Removing the package is crucial, but there is no guarantee that all malicious software will be removed. A thorough security assessment of your system is recommended.

How To Fix

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

npm uninstall log-symbols_updated

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