Critical Malicious Code Vulnerability in lstsyw Package

lstsyw Updated 19 Oct 2026

Summary

19/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18022: Malicious code in lstsyw (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The lstsyw package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate specific tasks within the Node.js ecosystem. However, this package has been identified as containing malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the lstsyw package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to a malicious actor who has inserted harmful code into the package, making any computer running it fully compromised. Users are advised to treat any system with this package installed as potentially controlled by an external entity.

How To Fix

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

npm uninstall lstsyw

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 other than removing the package entirely and ensuring that your system is secure. It is recommended to monitor your system for any unusual activity following the removal.

Conclusion

The lstsyw package has been identified as containing malicious code that compromises system security. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of your dependencies is crucial to prevent future vulnerabilities.

See every vulnerability recorded for lstsyw →

Share this vulnerability

FAQ

Immediately uninstall the lstsyw package using npm uninstall lstsyw and rotate any sensitive keys or secrets stored on the system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available for the lstsyw package. It is recommended to remove it entirely.

Failing to address this vulnerability can lead to unauthorized access to sensitive information and complete control of your system by malicious actors.

While this incident raises concerns, it is essential to review and monitor all packages you use. Tools like Vulert can help you stay informed about vulnerabilities.

How To Fix

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

npm uninstall lstsyw

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