Which versions of @alaska-its/design-tokens are malicious?

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

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

@alaska-its/design-tokens 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.

I already installed @alaska-its/design-tokens — how do I know if it already compromised me?

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

Yes — @alaska-its/design-tokens is associated with the RLMA-2025-00002, RLUA-2026-05802 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 @alaska-its/design-tokens 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 @alaska-its/design-tokens (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @alaska-its/design-tokens across your stack and pipelines.

Malicious package

@alaska-its/design-tokensnpm

@alaska-its/design-tokens is a confirmed malicious npm package (MAL-2025-756) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @alaska-its/design-tokens (npm)

MAL-2025-756

Immediate action

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

npm uninstall @alaska-its/design-tokens

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

54d738022ed87407e1a7dc4d00b9e338d84796c82562e1a8b25ba2bdc2b12787

eb768821f4e8917a82d15ae9d448ade9af8ed201bc8ff1d22d6156b97affad45

Detection & response playbook

Credential / info stealer

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

Campaign

RLMA-2025-00002RLUA-2026-05802

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @alaska-its/design-tokens-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database