Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @sporta-technology published 69 malicious packages. See the full campaign →
Malicious package

@sporta-technology/d11-web-components.design-tokensnpm

@sporta-technology/d11-web-components.design-tokens is a confirmed malicious npm package (MAL-2025-3322) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.46, 0.0.9999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sporta-technology/d11-web-components.design-tokens (npm)

MAL-2025-3322
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sporta-technology/d11-web-components.design-tokens

Malicious versions

2 flagged
0.0.460.0.9999

Indicators of compromise (SHA-256)

8cad2b45bf36170d2a2cc95697c2c775c6babea9042e00f42b9917d2ce6835bd

Detection & response playbook

Credential / info stealer

  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sporta-technology/d11-web-components.design-tokens (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sporta-technology/d11-web-components.design-tokens across your stack and pipelines.

  2. If you installed it — respond

    @sporta-technology/d11-web-components.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.

  3. Did it already run?

    If @sporta-technology/d11-web-components.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.

  4. How O3 protects you

    O3 blocks @sporta-technology/d11-web-components.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. @sporta-technology/d11-web-components.design-tokens on npm has been identified as a malicious package (versions 0.0.46, 0.0.9999 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-02069

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @sporta-technology/d11-web-components.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
@sporta-technology/d11-web-components.design-tokens (npm) malicious package — MAL-2025-3322 | O3 Security