What does the lingewindows malware do?

The package lingewindows was found to contain malicious code. The OpenSSF Package Analysis project identified 'lingewindows' @ 99.3.380452 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of lingewindows are malicious?

The following npm versions of lingewindows are flagged malicious: 99.3.380452. Treat any of these as compromised.

How do I remediate lingewindows if I installed it?

Remove lingewindows from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed lingewindows — how do I know if it already compromised me?

If lingewindows was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find lingewindows across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lingewindows (version 99.3.380452).

Malicious package

lingewindowsnpm

Advisory published Mar 21, 2026Updated Mar 23, 2026

lingewindows is a confirmed malicious npm package (MAL-2026-2015) that executes malicious code on install (malicious version 99.3.380452). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lingewindows (npm)

MAL-2026-2015

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall lingewindows

What this malware does

The package lingewindows was found to contain malicious code.

The OpenSSF Package Analysis project identified 'lingewindows' @ 99.3.380452 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

99.3.380452

Indicators of compromise (SHA-256)

e696256205c30e261ded5433b14a5b4d64d0afba5ec932a77ebcac248eceb80e

1764671c9ae79c37db80b846d9e8efe94714732160dda25659a8e96f7dadb39d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lingewindows (version 99.3.380452).
If you installed it — respond
Remove lingewindows from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If lingewindows was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. lingewindows on npm has been identified as a malicious package (version 99.3.380452 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks lingewindows-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database