CVE-2022-2931: Malicious code in expressyession (npm)

expressyession Updated 02 Oct 2025

Summary

19/08/2022
CRITICAL
No i
Critical
Not published

MAL-2022-2931: Malicious code in expressyession (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The expressyession package is an npm package used for managing sessions in Express.js applications. It provides functionality for session storage, retrieval, and manipulation. The package is widely used in web applications built with Express.js.

Vulnerability Detail

The expressyession package has been found to contain malicious code. Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

How To Fix

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

npm uninstall expressyession

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 expressyession package has been found to contain malicious code, compromising the security of any computer with the package installed or running. It is crucial to follow the recommended steps to mitigate the risk and ensure a clean and secure environment. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for expressyession →

Share this vulnerability

FAQ

The impact of this vulnerability is severe as it compromises the security of the affected computer. All secrets and keys stored on the computer should be rotated immediately to prevent unauthorized access.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and the tool will alert you if the expressyession package is present and compromised.

While removing the expressyession package is recommended, it may not completely remove all malicious software resulting from its installation. It is crucial to rotate all secrets and keys stored on the affected computer and perform a thorough security audit.

Yes, the recommended fix for this vulnerability is to rotate all secrets and keys stored on the affected computer, remove the expressyession package, and perform a security audit. Reinstalling the operating system may also be necessary to ensure a clean and secure environment.

If your computer is compromised, it is crucial to rotate all secrets and keys stored on that computer from a different computer. Remove the expressyession package and perform a thorough security audit. Consider reinstalling the operating system to ensure a clean and secure environment.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall expressyession

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