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

luftmvfiwgxydesnpm

luftmvfiwgxydes is a confirmed malicious npm package (MAL-2026-16398) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in luftmvfiwgxydes (npm)

MAL-2026-16398
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall luftmvfiwgxydes

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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.

Malicious versions

6 flagged
1.0.01.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

8cf9f25e87c3310292b60b507773f9689e59eeb6e950eb2e6a7c44b68deea04e
e487d10b32b0e42f4ed6478fa461451bcacc8eb9d679a58931bc474c339feae7
fb64eb8c74d0923f130f714ca2bc7ba2ab362a433f4e9b3f563fdcae03183f6d
41d62e6d0a9a8555c78c71faa4ebe161f6b7a5ac9419215792c1ac3608901ee6
59663215f42fb96acb764c67ff87861ebf486dcc607deab45471f57b60a7eafb
6a5a900c3b2701c9f65e8dedeadaab29999667adff183730cb2b9af575c957b5
94b98fbf56b3b886b1c555cae34cab1fc014cc3f748c08f72c5bbecb9a99565a

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 luftmvfiwgxydes (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging luftmvfiwgxydes across your stack and pipelines.

  2. If you installed it — respond

    Remove luftmvfiwgxydes 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 luftmvfiwgxydes 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 luftmvfiwgxydes 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. luftmvfiwgxydes on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j2f6-x53f-2qqfIN-MAL-2026-020418IN-MAL-2026-020417IN-MAL-2026-020411IN-MAL-2026-020413IN-MAL-2026-020412IN-MAL-2026-020415

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks luftmvfiwgxydes-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.

Explore

luftmvfiwgxydes (npm) malicious package — MAL-2026-16398 | O3 Security