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/aggregator-account-get-otb-by-accountnpm

@twork-data-services/aggregator-account-get-otb-by-account is a confirmed malicious npm package (MAL-2025-41460) that executes malicious code on install (malicious version 1.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @twork-data-services/aggregator-account-get-otb-by-account (npm)

MAL-2025-41460
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @twork-data-services/aggregator-account-get-otb-by-account

Malicious versions

1 flagged
1.99.0

Indicators of compromise (SHA-256)

b8a40e75675f9196e9045ee579d3f2d01857d8754db888765530790d22bab934

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/aggregator-account-get-otb-by-account (version 1.99.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @twork-data-services/aggregator-account-get-otb-by-account across your stack and pipelines.

  2. If you installed it — respond

    Remove @twork-data-services/aggregator-account-get-otb-by-account 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/aggregator-account-get-otb-by-account 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/aggregator-account-get-otb-by-account 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/aggregator-account-get-otb-by-account on npm has been identified as a malicious package (version 1.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04356

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @twork-data-services/aggregator-account-get-otb-by-account-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
@twork-data-services/aggregator-account-get-otb-by-account (npm) malicious package — MAL-2025-41460 | O3 Security