Which versions of umber-root are malicious?

The following npm versions of umber-root are flagged malicious: 1.1.0, 1.1.2. Treat any of these as compromised.

How do I remediate umber-root if I installed it?

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

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

Yes — umber-root is associated with the IN-MAL-2026-014943, IN-MAL-2026-014945 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 umber-root 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 umber-root (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging umber-root across your stack and pipelines.

Malicious package

umber-rootnpm

umber-root is a confirmed malicious npm package (MAL-2026-12814) that executes malicious code on install (malicious versions 1.1.0, 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in umber-root (npm)

MAL-2026-12814

Immediate action

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

npm uninstall umber-root

What this malware does

The npm postinstall lifecycle hook runs dist/config.js, which fetches JSON from https://my-api.trade-api.workers.dev?id=3 and then invokes globalThis[data.success](data.id), letting the remote endpoint choose which global (eval, Function, require, etc.) to call and with what argument. The package reassigns globalThis.require = require earlier in the same file to make require reachable through this indirection. The result is arbitrary code execution on every installer machine during npm install, with both the executor and its argument supplied by an attacker-controlled Cloudflare Workers endpoint. The package advertises itself as a color toolkit; there is no build or configuration purpose served by a network-dispatched global invocation, and the string-indexed global lookup is an evasion pattern that hides the sink from static scanners.

Malicious versions

2 flagged

1.1.01.1.2

Indicators of compromise (SHA-256)

a16b80d2c76699beaf0773da7233c1e136a951a8edd0ba84b073ea78590c23e1

a47da1a0e6cc80e91ba29f2baff3c412926050d2f5cff1441102734b96592769

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 umber-root (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging umber-root across your stack and pipelines.
If you installed it — respond
Remove umber-root 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 umber-root 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 umber-root 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. umber-root on npm has been identified as a malicious package (versions 1.1.0, 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014943IN-MAL-2026-014945

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks umber-root-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