Malicious code in exnessimo (npm)

exnessimo Updated 02 Oct 2025

Summary

06/11/2023
CRITICAL
No i
Critical
Not published

MAL-2023-8456: Malicious code in exnessimo (npm). Affects exnessimo versions 1999.99.9. 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 exnessimo package is an npm package used for [provide brief description of the package's functionality and key attributes]. It is vulnerable to a malicious code injection, which can compromise the security of any computer that has this package installed or running.

Vulnerability Detail

The vulnerability, identified as MAL-2023-8456, involves the presence of malicious code in the exnessimo package. This code can give full control of the affected computer to an external entity, compromising any secrets and keys stored on that computer. Removing the package may not guarantee the removal of all malicious software resulting from its installation.

How To Fix

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

npm uninstall exnessimo

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

No workaround is available for this vulnerability. It is essential to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The presence of malicious code in the exnessimo package poses a significant security risk. It is crucial to take immediate action by rotating all secrets and keys stored on the affected computer and removing the package. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for exnessimo →

Share this vulnerability

FAQ

This vulnerability can result in a complete compromise of the affected computer, allowing an external entity to gain full control. Any secrets and keys stored on the computer should be considered compromised.

If you have the exnessimo package installed or running, your computer may be affected. It is recommended to check for the presence of the package and take appropriate actions.

While removing the exnessimo package is a necessary step, it may not completely eliminate all malicious software that may have been installed. It is crucial to rotate all secrets and keys stored on the affected computer from a different computer.

The primary mitigation for this vulnerability is to rotate all secrets and keys stored on the affected computer from a different computer. Additionally, removing the exnessimo package is recommended.

You can find more information about this vulnerability in the provided source link: [source link]

How To Fix

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

npm uninstall exnessimo

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