CVE-2022-2898: Malicious code in evernote-sdk-sample-node (npm)

evernote-sdk-sample-node Updated 02 Oct 2025

Summary

05/10/2022
CRITICAL
No i
Critical
Not published

MAL-2022-2898: Malicious code in evernote-sdk-sample-node (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 evernote-sdk-sample-node package is an npm package that provides a sample implementation of the Evernote SDK for Node.js. It allows developers to interact with the Evernote API and build applications that integrate with Evernote. The package is widely used by developers to create Evernote-related functionality in their Node.js applications.

Vulnerability Detail

The evernote-sdk-sample-node package has been found to contain malicious code. This code can compromise the security of any computer that has the package installed or running. Once installed, the malicious code gives full control of the computer to an outside entity, potentially exposing any secrets and keys stored on that computer. It is highly recommended to rotate all secrets and keys stored on affected computers immediately from a different 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 evernote-sdk-sample-node

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 known workaround for this vulnerability. It is crucial to follow the steps mentioned in the 'how_to_fix' section to mitigate the risk.

Conclusion

The evernote-sdk-sample-node package has been found to contain malicious code, posing a significant security risk to any computer with the package installed or running. It is crucial to follow the recommended steps to mitigate the vulnerability, including rotating secrets and keys, removing the package, and conducting a security audit. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for evernote-sdk-sample-node →

Share this vulnerability

FAQ

The impact of this vulnerability is severe. Any computer with the evernote-sdk-sample-node package installed or running is considered fully compromised, and all secrets and keys stored on that computer should be rotated immediately.

If you have the evernote-sdk-sample-node package installed or running on your computer, it is likely affected. It is recommended to conduct a thorough security audit to ensure the presence of any malicious software.

While removing the evernote-sdk-sample-node package is necessary, it may not guarantee the complete removal of all malicious software resulting from its installation. It is crucial to rotate all secrets and keys stored on affected computers and conduct a security audit.

No, there is no specific patch available for this vulnerability. The recommended steps to fix the vulnerability involve rotating secrets and keys, removing the package, and conducting a security audit.

To prevent this vulnerability in the future, it is essential to regularly update and monitor the packages used in your applications. Stay informed about any security advisories or vulnerability reports related to the packages you rely on.

How To Fix

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

npm uninstall evernote-sdk-sample-node

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