Which versions of @squawk/notams are malicious?

The following npm versions of @squawk/notams are flagged malicious: 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10. Treat any of these as compromised.

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

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

If @squawk/notams was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @squawk/notams part of a known attack campaign?

Yes — @squawk/notams is associated with the GHSA-4qm3-vxjm-3wfp 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/notams across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @squawk/notams (5 malicious versions).

Part of a larger attack: @squawk published 22 malicious packages. See the full campaign →

Malicious package

@squawk/notamsnpm

Advisory published May 12, 2026Updated May 12, 2026

@squawk/notams is a confirmed malicious npm package (MAL-2026-3451) that steals credentials and exfiltrates sensitive data (malicious versions 0.3.6, 0.3.7, 0.3.8…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @squawk/notams (npm)

MAL-2026-3451

Immediate action

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

npm uninstall @squawk/notams

What this malware does

The package @squawk/notams 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.60.3.70.3.80.3.90.3.10

Indicators of compromise (SHA-256)

fd709d66feb81a447d1379117eed1ac084a296695f6c19561e0f9048c46abd49

5d4d0088e65148806fd02e5f3832c7f5d93f15cb02f31c8b38c78469aef2fa45

5e1924464368f0c5816ee84e000cc47017f44045140feafbbc9e685d847ed5a5

c1516c9c418f64f53d6e8e9ac55eb838fcaa40df0d637553dce1dc3569823edb

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @squawk/notams (5 malicious versions).
If you installed it — respond
@squawk/notams 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/notams was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @squawk/notams on npm has been identified as a malicious package (versions 0.3.6, 0.3.7, 0.3.8, 0.3.9, 0.3.10 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4qm3-vxjm-3wfp

References

Credits

Amazon Inspector · finder

Detect & block this

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