Which versions of @squawk/airports are malicious?

The following npm versions of @squawk/airports are flagged malicious: 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.6. Treat any of these as compromised.

How do I remediate @squawk/airports if I installed it?

@squawk/airports is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @squawk/airports — how do I know if it already compromised me?

If @squawk/airports 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 @squawk/airports part of a known attack campaign?

Yes — @squawk/airports is associated with the GHSA-r594-chgw-g4p9 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 @squawk/airports 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 @squawk/airports (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @squawk/airports across your stack and pipelines.

Malicious package

@squawk/airportsnpm

Malicious code in @squawk/airports (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3436

Immediate action

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

npm uninstall @squawk/airports

What this malware does

The package @squawk/airports was found to contain 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.

This package was compromised as part of the "Mini Shai-Hulud is back" worm by the TeamPCP threat actor.

The package will steal credentials and then propogate it to every package it has access to. The package also attempts to remain persistent.

Malicious versions

5 flagged

0.6.20.6.30.6.40.6.50.6.6

Indicators of compromise (SHA-256)

f8adf8853b03c99d84b919062f8c688b4bfb42f72cc9de33299fe3e3f9a2b92b

fde560d948231801181d4ac141ad427e2684ab698a2e24435ca0e7df01ce88f9

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

01fabaad6adcf6ba78ba71fb750d70c8e3f3a1e524a75a6b8bf8ddc7769ac5b0

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @squawk/airports (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @squawk/airports across your stack and pipelines.
If you installed it — respond
@squawk/airports is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @squawk/airports 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 @squawk/airports 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. @squawk/airports on npm has been identified as a malicious package (versions 0.6.2, 0.6.3, 0.6.4, 0.6.5, 0.6.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-r594-chgw-g4p9

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @squawk/airports-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring