Which versions of @squawk/airspace-data are malicious?

The following npm versions of @squawk/airspace-data are flagged malicious: 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.5.7. Treat any of these as compromised.

How do I remediate @squawk/airspace-data if I installed it?

@squawk/airspace-data 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/airspace-data — how do I know if it already compromised me?

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

Yes — @squawk/airspace-data is associated with the GHSA-j5w5-5fj6-mwvv 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/airspace-data 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/airspace-data (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/airspace-data across your stack and pipelines.

Malicious package

@squawk/airspace-datanpm

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

MAL-2026-3438

Immediate action

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

npm uninstall @squawk/airspace-data

What this malware does

The package @squawk/airspace-data 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.5.30.5.40.5.50.5.60.5.7

Indicators of compromise (SHA-256)

0b4e161f94d131de72860067a9d14f32ceeb65873eaab0f6b7e73a52f78a1114

c54e09ce701d0836e4ab95dd0613028ae9f69046e6a3ecb2c7bb2b116b545d2d

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

97ec562ed3f6b81b4a80634791292522df833be8bff61cf147cacca7dd5fb403

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/airspace-data (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/airspace-data across your stack and pipelines.
If you installed it — respond
@squawk/airspace-data 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/airspace-data 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/airspace-data 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/airspace-data on npm has been identified as a malicious package (versions 0.5.3, 0.5.4, 0.5.5, 0.5.6, 0.5.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j5w5-5fj6-mwvv

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @squawk/airspace-data-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