What does the icon-service malware do?

The package icon-service was found to contain malicious code. The OpenSSF Package Analysis project identified 'icon-service' @ 5.0.0 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of icon-service are malicious?

The following npm versions of icon-service are flagged malicious: 1.2.3, 1.2.4, 2.0.0, 2.0.1, 3.0.0, 4.0.0, 5.0.0. Treat any of these as compromised.

How do I remediate icon-service if I installed it?

Remove icon-service 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 icon-service — how do I know if it already compromised me?

If icon-service 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 icon-service part of a known attack campaign?

Yes — icon-service is associated with the RLMA-2026-01349 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 icon-service across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for icon-service (7 malicious versions).

Malicious package

icon-servicenpm

Advisory published Jan 8, 2026Updated Mar 19, 2026

icon-service is a confirmed malicious npm package (MAL-2026-167) that executes malicious code on install (malicious versions 1.2.3, 1.2.4, 2.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in icon-service (npm)

MAL-2026-167

Immediate action

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

npm uninstall icon-service

What this malware does

The package icon-service was found to contain malicious code.

The OpenSSF Package Analysis project identified 'icon-service' @ 5.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

7 flagged

1.2.31.2.42.0.02.0.13.0.04.0.05.0.0

Indicators of compromise (SHA-256)

4f7301fe52d8afbc08b8694f47c110b415a32cb3fa5775dc536544ea42f1661a

c036555d918021fafe661296499aab549fac428c2b9cefb72670f63914dfa974

7d07b5edac35a1aa92b47a2e958b9795b808b7d4af34a8f29b607deac5790d6b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for icon-service (7 malicious versions).
If you installed it — respond
Remove icon-service 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 icon-service 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. icon-service on npm has been identified as a malicious package (versions 1.2.3, 1.2.4, 2.0.0, 2.0.1, 3.0.0, 4.0.0, 5.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01349

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks icon-service-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