Which versions of @squawk/fixes are malicious?

The following npm versions of @squawk/fixes are flagged malicious: 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6. Treat any of these as compromised.

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

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

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

Yes — @squawk/fixes is associated with the GHSA-rjx4-mpv7-fwq9 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/fixes 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/fixes (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/fixes across your stack and pipelines.

Malicious package

@squawk/fixesnpm

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

MAL-2026-3442

Immediate action

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

npm uninstall @squawk/fixes

What this malware does

The package @squawk/fixes 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.3.20.3.30.3.40.3.50.3.6

Indicators of compromise (SHA-256)

9b4ba8be3823ebe8f019d37fa681809a96867a646eeb679dd22682070aa9f570

85af8ac7e30ac09fffd183b49d3ffe1d75f41b3019556f8a984024a49b7f33f4

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

7c1b4eb0a49d55989cadcce8bda40c86dc03e5776c450cd9643e5b3f43811a87

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/fixes (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/fixes across your stack and pipelines.
If you installed it — respond
@squawk/fixes 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/fixes 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/fixes 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/fixes on npm has been identified as a malicious package (versions 0.3.2, 0.3.3, 0.3.4, 0.3.5, 0.3.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rjx4-mpv7-fwq9

References

Credits

Amazon Inspector · finder

Detect & block this

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