Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

lingewindowsnpm

Malicious code in lingewindows (npm) Remove it immediately and rotate any exposed credentials.

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for lingewindows (version 99.3.380452). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lingewindows across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If lingewindows was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks lingewindows before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

lingewindows (npm) malicious package — MAL-2026-2015 | O3 Security