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.date-picker.time-pickernpm

@sporta-technology/d11-web-components.date-picker.time-picker is a confirmed malicious npm package (MAL-2025-3321) that executes malicious code on install (malicious versions 0.0.56, 0.0.9999). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @sporta-technology/d11-web-components.date-picker.time-picker (npm)

MAL-2025-3321
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sporta-technology/d11-web-components.date-picker.time-picker

Malicious versions

2 flagged
0.0.560.0.9999

Indicators of compromise (SHA-256)

01765397036c8c0804e0f1bd0b7e6c2f0152f8e36fd0d02207032c1b42c49155

Detection & response playbook

Malicious package
  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.date-picker.time-picker (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.date-picker.time-picker across your stack and pipelines.

  2. If you installed it — respond

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

  3. Did it already run?

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

Campaign

RLMA-2025-02068

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @sporta-technology/d11-web-components.date-picker.time-picker-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.

Explore

@sporta-technology/d11-web-components.date-picker.time-picker (npm) malicious package — MAL-2025-3321 | O3 Security