Which versions of @squawk/icao-registry are malicious?

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

How do I remediate @squawk/icao-registry if I installed it?

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

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

Yes — @squawk/icao-registry is associated with the GHSA-mpc4-8622-ww9c 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/icao-registry 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/icao-registry (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/icao-registry across your stack and pipelines.

Malicious package

@squawk/icao-registrynpm

@squawk/icao-registry is a confirmed malicious npm package (MAL-2026-3446) that steals credentials and exfiltrates sensitive data (malicious versions 0.5.2, 0.5.3, 0.5.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @squawk/icao-registry (npm)

MAL-2026-3446

Immediate action

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

npm uninstall @squawk/icao-registry

What this malware does

The package @squawk/icao-registry 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.20.5.30.5.40.5.50.5.6

Indicators of compromise (SHA-256)

636fec1fc24c7e2a888308c109090267875d3262b00129dee2fab20ae7d532c5

90d07aa7b6e9f45ba54af3c9c9ced274ebe2e92804820b113eee146618205c47

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

3cdcc18fc8342a0ce7e7b2f3751bcb7d6e64c3fe660a9c5836f6d06aac4a4b45

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

Campaign

GHSA-mpc4-8622-ww9c

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @squawk/icao-registry-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

Explore

All malware advisories How O3 detects malware Vulnerability database