Which versions of integration-icons are malicious?

The following npm versions of integration-icons are flagged malicious: 100.0.0. Treat any of these as compromised.

How do I remediate integration-icons if I installed it?

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

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

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

Search your lockfiles and build artifacts for integration-icons (version 100.0.0).

Malicious package

integration-iconsnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

integration-icons is a confirmed malicious npm package (MAL-2026-1750) that executes malicious code on install (malicious version 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in integration-icons (npm)

MAL-2026-1750

Immediate action

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

npm uninstall integration-icons

What this malware does

The package integration-icons was found to contain malicious code.

Malicious versions

1 flagged

100.0.0

Indicators of compromise (SHA-256)

7c0a148d61bad3ad7394ed38864b9904cce561bfad43ba69c027247d771eee24

7e95fefd16e8add2fde660440ba109cf81efb9e91e10fba318a4733ae3fbf9c7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for integration-icons (version 100.0.0).
If you installed it — respond
Remove integration-icons 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 integration-icons 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. integration-icons on npm has been identified as a malicious package (version 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01356

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks integration-icons-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