Which versions of @postman/aether-icons are malicious?

The following npm versions of @postman/aether-icons are flagged malicious: 2.23.2, 2.23.3, 2.23.4. Treat any of these as compromised.

How do I remediate @postman/aether-icons if I installed it?

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

If @postman/aether-icons 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 @postman/aether-icons part of a known attack campaign?

Yes — @postman/aether-icons is associated with the GHSA-pr99-cvwr-49x5, RLMA-2025-06037 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 @postman/aether-icons 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 @postman/aether-icons (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @postman/aether-icons across your stack and pipelines.

Malicious package

@postman/aether-iconsnpm

Malicious code in @postman/aether-icons (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190676

Immediate action

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

npm uninstall @postman/aether-icons

What this malware does

The package @postman/aether-icons 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 by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

3 flagged

2.23.22.23.32.23.4

Indicators of compromise (SHA-256)

bc111a3f76c40671d86c10b02a24fed21d201d1689248b37303cfe610df7cf6a

cf4244dc3aeb4aeef61e6a25bf53dd406e67c8b3d33f710a91934f64a631ae69

c8cd704b2460e284797e6f9afb03f34cdf2f85b5abbd3e9e547cbc37707c6698

ce995fd242e4f62933f3d9342115251051ebebf39f708734b75cae4037b2dc25

d39513f4f0d604ef915edd75d46a42734f498c2569803a62fea93b748c59b8a4

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 @postman/aether-icons (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @postman/aether-icons across your stack and pipelines.
If you installed it — respond
@postman/aether-icons 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 @postman/aether-icons 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 @postman/aether-icons 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. @postman/aether-icons on npm has been identified as a malicious package (versions 2.23.2, 2.23.3, 2.23.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pr99-cvwr-49x5RLMA-2025-06037

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @postman/aether-icons-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