Which versions of @egencia/design-tokens are malicious?

The following npm versions of @egencia/design-tokens are flagged malicious: 99.99.9. Treat any of these as compromised.

How do I remediate @egencia/design-tokens if I installed it?

Remove @egencia/design-tokens 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 @egencia/design-tokens — how do I know if it already compromised me?

If @egencia/design-tokens 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 @egencia/design-tokens part of a known attack campaign?

Yes — @egencia/design-tokens is associated with the RLMA-2026-10625 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 @egencia/design-tokens across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @egencia/design-tokens (version 99.99.9).

Part of a larger attack: @egencia published 8 malicious packages. See the full campaign →

Malicious package

@egencia/design-tokensnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

@egencia/design-tokens is a confirmed malicious npm package (MAL-2026-16515) that executes malicious code on install (malicious version 99.99.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @egencia/design-tokens (npm)

MAL-2026-16515

Immediate action

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

npm uninstall @egencia/design-tokens

Malicious versions

1 flagged

99.99.9

Indicators of compromise (SHA-256)

beef43ad83e0bf3f4b78d2ac4a8bfad22d0772124d8ec7e23973edc4000c31c8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10625

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @egencia/design-tokens-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