Malicious code in @lognex/notifications (npm)

@lognex/notifications Updated 02 Oct 2025

Summary

29/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8631: Malicious code in @lognex/notifications (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 @lognex/notifications package is an npm package that provides functionality for handling notifications in applications. It is commonly used in various JavaScript projects. However, this package has been found to contain malicious code, which poses a significant security risk to any computer that has it installed or running.

Vulnerability Detail

The malicious code in @lognex/notifications has been identified as a serious threat. It is advised to consider any computer with this package installed as fully compromised. This means that all secrets and keys stored on that computer should be rotated immediately from a different computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation. The code appears to be embedded with malicious intent, potentially allowing an outside entity to gain full control of the compromised computer.

How To Fix

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

npm uninstall @lognex/notifications

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 is no specific workaround mentioned for this vulnerability. It is crucial to follow the steps outlined in the 'how_to_fix' section to mitigate the risk and ensure the security of the affected computer.

Conclusion

The presence of malicious code in the @lognex/notifications package poses a significant security risk to any computer with it installed. It is crucial to take immediate action by rotating secrets and keys, removing the package, and conducting a thorough security audit. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for @lognex/notifications →

Share this vulnerability

FAQ

The @lognex/notifications package is an npm package used for handling notifications in JavaScript applications.

The malicious code in @lognex/notifications can compromise the security of your computer, potentially allowing an outside entity to gain full control and access to sensitive information stored on that computer.

If you have @lognex/notifications installed on your computer, it is recommended to rotate all secrets and keys stored on that computer from a different, secure computer. Additionally, remove the package and conduct a thorough security audit to ensure no other malicious software or code is present.

While removing the @lognex/notifications package is advised, it may not guarantee the removal of all malicious software that may have been installed as a result. It is crucial to conduct a thorough security audit to ensure the complete removal of any malicious software or code.

To prevent similar vulnerabilities in the future, it is important to regularly update and patch all software and packages used in your application. Stay informed about security advisories and follow best practices for secure coding and package management.

How To Fix

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

npm uninstall @lognex/notifications

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