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/proxy-invest-api-v1-customer-broker-accountsnpm

Advisory published Updated

@twork-data-services/proxy-invest-api-v1-customer-broker-accounts is a confirmed malicious npm package (MAL-2025-41504) that executes malicious code on install (malicious versions 0.99.0, 1.99.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @twork-data-services/proxy-invest-api-v1-customer-broker-accounts (npm)

MAL-2025-41504
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @twork-data-services/proxy-invest-api-v1-customer-broker-accounts

Malicious versions

2 flagged
0.99.01.99.0

Indicators of compromise (SHA-256)

5ace2a35935f02beae0fe56b6637fd7a157f228aca0e23a2f8bcc6c2e382b105

Detection & response playbook

Malicious package

  1. Find it

    Search your lockfiles and build artifacts for @twork-data-services/proxy-invest-api-v1-customer-broker-accounts (2 malicious versions).

  2. If you installed it — respond

    Remove @twork-data-services/proxy-invest-api-v1-customer-broker-accounts 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/proxy-invest-api-v1-customer-broker-accounts was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @twork-data-services/proxy-invest-api-v1-customer-broker-accounts on npm has been identified as a malicious package (versions 0.99.0, 1.99.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04400

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks @twork-data-services/proxy-invest-api-v1-customer-broker-accounts-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/proxy-invest-api-v1-customer-broker-accounts (npm) malicious package — MAL-2025-41504 | O3 Security