What does the @ssgw/icon malware do?

The OpenSSF Package Analysis project identified '@ssgw/icon' @ 9.999.999 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity.

Which versions of @ssgw/icon are malicious?

The following npm versions of @ssgw/icon are flagged malicious: 9.999.999. Treat any of these as compromised.

How do I remediate @ssgw/icon if I installed it?

Remove @ssgw/icon from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @ssgw/icon — how do I know if it already compromised me?

If @ssgw/icon 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.

How do I find @ssgw/icon across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @ssgw/icon (version 9.999.999).

Malicious package

@ssgw/iconnpm

Advisory published Aug 10, 2026Updated Aug 10, 2026

@ssgw/icon is a confirmed malicious npm package (MAL-2026-13684) that executes malicious code on install (malicious version 9.999.999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ssgw/icon (npm)

MAL-2026-13684

Immediate action

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

npm uninstall @ssgw/icon

What this malware does

The OpenSSF Package Analysis project identified '@ssgw/icon' @ 9.999.999 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

9.999.999

Indicators of compromise (SHA-256)

9d2fb7b19baedba9c5350b19ebf8ab3e99be16bd04fd15a3960889766ed97e70

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @ssgw/icon (version 9.999.999).
If you installed it — respond
Remove @ssgw/icon from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @ssgw/icon 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. @ssgw/icon on npm has been identified as a malicious package (version 9.999.999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @ssgw/icon-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database