Which versions of @twork-data-services/prime-customer-products are malicious?

The following npm versions of @twork-data-services/prime-customer-products are flagged malicious: 0.99.0, 1.99.0. Treat any of these as compromised.

How do I remediate @twork-data-services/prime-customer-products if I installed it?

Remove @twork-data-services/prime-customer-products 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.

I already installed @twork-data-services/prime-customer-products — how do I know if it already compromised me?

If @twork-data-services/prime-customer-products 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.

Is @twork-data-services/prime-customer-products part of a known attack campaign?

Yes — @twork-data-services/prime-customer-products is associated with the RLMA-2025-04396 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @twork-data-services/prime-customer-products across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @twork-data-services/prime-customer-products (2 malicious versions).

Part of a larger attack: @twork-data-services published 70 malicious packages. See the full campaign →

Malicious package

@twork-data-services/prime-customer-productsnpm

Advisory published Aug 28, 2025Updated Aug 28, 2025

@twork-data-services/prime-customer-products is a confirmed malicious npm package (MAL-2025-41500) 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/prime-customer-products (npm)

MAL-2025-41500

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @twork-data-services/prime-customer-products

Malicious versions

2 flagged

0.99.01.99.0

Indicators of compromise (SHA-256)

7d0294be254de565d44f39aa17035cac675e3df085a33db42fb4f29955f9fb16

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @twork-data-services/prime-customer-products (2 malicious versions).
If you installed it — respond
Remove @twork-data-services/prime-customer-products 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.
Did it already run?
If @twork-data-services/prime-customer-products 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/prime-customer-products 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-04396

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @twork-data-services/prime-customer-products-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