Which versions of commons-ui-styles are malicious?

The following npm versions of commons-ui-styles are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate commons-ui-styles if I installed it?

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

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

Yes — commons-ui-styles is associated with the IN-MAL-2026-005038, IN-MAL-2026-005037, GHSA-3w2q-76fx-mcgj, RLMA-2026-05519 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 commons-ui-styles 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 commons-ui-styles (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commons-ui-styles across your stack and pipelines.

Malicious package

commons-ui-stylesnpm

Malicious code in commons-ui-styles (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-5437

Immediate action

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

npm uninstall commons-ui-styles

What this malware does

[email protected] is an empty placeholder package (index.js exports {}, description/author blank, version bumped to 99.9.1 — the classic dependency-confusion override shape) whose only on-install effect is dependency resolution. Its package.json declares a transitive dependency ltidisafe resolved from a hardcoded non-registry tarball URL (https://ltidi.storage.googleapis.com/depenconf/ltidisafe-2.9.6.tgz) on a Google Cloud Storage bucket. The path segment literally contains depenconf, indicating dependency-confusion tooling. On npm install commons-ui-styles, npm fetches whatever bytes that bucket currently serves and installs them as a dependency; any preinstall/install/postinstall lifecycle scripts in the fetched tarball run on the installer's host. The bucket owner controls the payload contents at any time, with no version pinning to the npm registry, no integrity check beyond what npm computes against the live download, and no relationship to a documented publisher.

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.

Malicious versions

1 flagged

99.9.1

Indicators of compromise (SHA-256)

0e7b193f10d4887360722fe1f0898f3bf456faceeaf7e7c6be801c6fc45d7d77

8b9fb701d18bde61d1dc783f0575a4d83bc0eba2653bd0832d0fc26bc9e85b48

0e1b59b1a66b5b52881d2f9babca5a402325f4454444f4e318670406c17ae780

c8183488d1e4cd5c3d0a1fa6a9b8cb855d7366a19c4b3ff43db575e6c21f757d

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for commons-ui-styles (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging commons-ui-styles across your stack and pipelines.
If you installed it — respond
Remove commons-ui-styles 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 commons-ui-styles 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 commons-ui-styles 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. commons-ui-styles on npm has been identified as a malicious package (version 99.9.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-005038IN-MAL-2026-005037GHSA-3w2q-76fx-mcgjRLMA-2026-05519

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks commons-ui-styles-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