Which versions of platform-ui-colors are malicious?

The following npm versions of platform-ui-colors are flagged malicious: 35.8.1. Treat any of these as compromised.

How do I remediate platform-ui-colors if I installed it?

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

If platform-ui-colors 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 platform-ui-colors part of a known attack campaign?

Yes — platform-ui-colors is associated with the IN-MAL-2026-017012 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 platform-ui-colors across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for platform-ui-colors (version 35.8.1).

Malicious package

platform-ui-colorsnpm

Advisory published Aug 7, 2026Updated Aug 7, 2026

platform-ui-colors is a confirmed malicious npm package (MAL-2026-13603) that executes malicious code on install (malicious version 35.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in platform-ui-colors (npm)

MAL-2026-13603

Immediate action

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

npm uninstall platform-ui-colors

What this malware does

On require of platform-ui-colors, both the declared main lib/telemetry.js and helpers.js fetch an opaque binary from author-controlled Cloudflare Workers hosts assembled from split string literals (oob-worker.cf100-416.workers.dev, oob-worker.cf101-adf.workers.dev, oob-worker.cf102-baf.workers.dev) with a DNS-TXT fallback to *.dl.wel1.ru, write it to /tmp/.cache<uid> or %TEMP%\dotnet_diag_<uid>.exe, chmod 755 the file, and detached-spawn it via cp.spawn('/bin/sh', ['-c', filePath+' &'], {detached:true}). Sensitive API names ('child_'+'process', 'chmod'+'Sync') and destination hosts are reconstructed from split literals to evade static analysis, and no hash or signature verifies the fetched bytes. Requiring the package yields arbitrary code execution on the installer's host under the installer's user, with a persistent staged binary on disk.

Malicious versions

1 flagged

35.8.1

Indicators of compromise (SHA-256)

118252cd198a6c0e985917992969dbbaf8e9792ccbc27fab0ebbab191a1e6023

Detection & response playbook

Malicious package

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

Campaign

IN-MAL-2026-017012

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks platform-ui-colors-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