Which versions of @squawk/weather are malicious?

The following npm versions of @squawk/weather are flagged malicious: 0.5.6, 0.5.7, 0.5.8, 0.5.9, 0.5.10. Treat any of these as compromised.

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

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

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

Yes — @squawk/weather is associated with the GHSA-p6w9-58xc-257f 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/weather 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/weather (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/weather across your stack and pipelines.

Malicious package

@squawk/weathernpm

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

MAL-2026-3456

Immediate action

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

npm uninstall @squawk/weather

What this malware does

The package @squawk/weather 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.60.5.70.5.80.5.90.5.10

Indicators of compromise (SHA-256)

71445d30bdef8256424a60e0abf2f5e2ce43b8c7dffa1476bd2ee7001013720f

f30739ffd21fae10f9256e54e4ab695b09b8f5ccf2beea6929ca61b52ed2f516

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

72341a088009d96497c994e0a076b60b00bf65b365831ef16abe360f5c6cf874

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

Campaign

GHSA-p6w9-58xc-257f

References

Credits

Amazon Inspector · finder

Detect & block this

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