Which versions of flight-suit are malicious?

The following npm versions of flight-suit are flagged malicious: 1.1.235, 1.1.25053, 1.1.25054, 1.1.25055. Treat any of these as compromised.

How do I remediate flight-suit if I installed it?

Remove flight-suit 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 flight-suit — how do I know if it already compromised me?

If flight-suit 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.

Is flight-suit part of a known attack campaign?

Yes — flight-suit is associated with the GHSA-ppmp-644r-w985, RLMA-2025-05371, RLUA-2025-05795 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find flight-suit across my projects, lockfiles, and CI pipelines?

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

Malicious package

flight-suitnpm

flight-suit is a confirmed malicious npm package (MAL-2025-48292) that executes malicious code on install (malicious versions 1.1.235, 1.1.25053, 1.1.25054…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in flight-suit (npm)

MAL-2025-48292

Immediate action

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

npm uninstall flight-suit

What this malware does

The package communicates with a domain associated with malicious activity.

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

4 flagged

1.1.2351.1.250531.1.250541.1.25055

Indicators of compromise (SHA-256)

6a6d36537b116f54f862bfade62a56a5be6181faa17c245d41201c57b229ae4e

2e560bae01f18db1241774cce534fbc093313c55af1fcd743f9159ba5b4b7ea7

e47801ad8ef632279829bf0bda3b3ee2e962beaf797031ad3ad96e6368f65767

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for flight-suit (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging flight-suit across your stack and pipelines.
If you installed it — respond
Remove flight-suit 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 flight-suit 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.
How O3 protects you
O3 blocks flight-suit 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. flight-suit on npm has been identified as a malicious package (versions 1.1.235, 1.1.25053, 1.1.25054, 1.1.25055 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-ppmp-644r-w985RLMA-2025-05371RLUA-2025-05795

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks flight-suit-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