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

@twork-data-services/customer-storage-api-v3-customer-timezonenpm

@twork-data-services/customer-storage-api-v3-customer-timezone is a confirmed malicious npm package (MAL-2025-41495) that executes malicious code on install (malicious versions 0.99.0, 1.99.0, 2.99.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @twork-data-services/customer-storage-api-v3-customer-timezone (npm)

MAL-2025-41495
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @twork-data-services/customer-storage-api-v3-customer-timezone

Malicious versions

12 flagged
0.99.01.99.02.99.03.99.04.99.05.99.06.99.07.99.08.99.09.99.010.99.099.99.0

Indicators of compromise (SHA-256)

2664681b3dc68d9fe78d26705e10747c834b89d3ad20ffec4a6b915300c662d2

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 @twork-data-services/customer-storage-api-v3-customer-timezone (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @twork-data-services/customer-storage-api-v3-customer-timezone across your stack and pipelines.

  2. If you installed it — respond

    Remove @twork-data-services/customer-storage-api-v3-customer-timezone 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 @twork-data-services/customer-storage-api-v3-customer-timezone 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 @twork-data-services/customer-storage-api-v3-customer-timezone 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. @twork-data-services/customer-storage-api-v3-customer-timezone on npm has been identified as a malicious package (versions 0.99.0, 1.99.0, 2.99.0, 3.99.0, 4.99.0, 5.99.0, 6.99.0, 7.99.0, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04391

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @twork-data-services/customer-storage-api-v3-customer-timezone-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

@twork-data-services/customer-storage-api-v3-customer-timezone (npm) malicious package — MAL-2025-41495 | O3 Security