Malicious Code Detected in 'lingewindows' Package - npm Vulnerability Alert

lingewindows Updated 21 Mar 2026

Summary

21/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2015: Malicious code in lingewindows (npm). Affects lingewindows versions 99.3.380452. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The 'lingewindows' package, available on npm, is designed for managing and manipulating window functionalities in JavaScript applications. It is widely used due to its ease of integration and robust features. However, recent analysis has revealed that this package has been compromised, posing significant security risks to users who have it installed.

Vulnerability Detail

The vulnerability in the 'lingewindows' package stems from its malicious behavior, which includes communication with a domain linked to harmful activities and the execution of commands that can compromise user systems. This malicious code can lead to unauthorized access, data breaches, and potential system damage, making it critical for users to address this issue promptly.

How To Fix

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

npm uninstall lingewindows

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

As a temporary workaround, users can remove the 'lingewindows' package from their projects until a secure version is confirmed. This can be achieved by executing the command: 'npm uninstall lingewindows'.

Conclusion

The 'lingewindows' package has been identified as malicious, posing significant risks to users. It is crucial to update or remove the package to safeguard your applications. Utilizing tools like Vulert can help monitor vulnerabilities effectively.

See every vulnerability recorded for lingewindows →

Share this vulnerability

FAQ

The 'lingewindows' package is a JavaScript library used for managing window functionalities in applications.

The malicious behavior was identified by the OpenSSF Package Analysis project, which flagged the package for its communication with a harmful domain and execution of malicious commands.

Using the compromised package can lead to unauthorized access, data breaches, and potential damage to user systems.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

If you cannot update the package right away, consider uninstalling it temporarily to prevent potential security risks.

How To Fix

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

npm uninstall lingewindows

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