NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

cilm-ui-commonsnpm

Advisory published Updated

cilm-ui-commons is a confirmed malicious npm package (MAL-2026-13943) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cilm-ui-commons (npm)

MAL-2026-13943
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall cilm-ui-commons

What this malware does

On npm install, the preinstall hook executes index.js which collects host identity data (os.hostname(), os.userInfo().username, os.homedir(), current working directory, DNS server list) together with the full package.json contents and POSTs them to the hardcoded external endpoint https://eogo57c0daum9d3.m.pipedream.net. The behavior fires unconditionally at install time on every installer machine. A code comment references burpcollaborator/Interactsh-style beaconing, consistent with dependency-confusion reconnaissance: the beacon fires when a private internal package name is inadvertently resolved from the public npm registry, revealing the victim's internal infrastructure to whoever controls the pipedream endpoint. The exfiltrated fields identify the installer's host, user account, filesystem layout, network DNS configuration, and internal package/dependency graph.

Malicious versions

1 flagged
1.1.0

Indicators of compromise (SHA-256)

008641dff89b7e4b86993671997e965642fab5620006c5ece0827f0fe72fe0d9

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for cilm-ui-commons (version 1.1.0).

  2. If you installed it — respond

    cilm-ui-commons is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If cilm-ui-commons 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. cilm-ui-commons on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017652

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks cilm-ui-commons-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

cilm-ui-commons (npm) malicious package — MAL-2026-13943 | O3 Security