Which versions of business-data are malicious?

The following npm versions of business-data are flagged malicious: 99.13.9, 99.31.9. Treat any of these as compromised.

How do I remediate business-data if I installed it?

Remove business-data 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 business-data — how do I know if it already compromised me?

If business-data 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 business-data part of a known attack campaign?

Yes — business-data is associated with the RLMA-2026-01903 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 business-data across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for business-data (2 malicious versions).

Malicious package

business-datanpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

business-data is a confirmed malicious npm package (MAL-2026-2737) that executes malicious code on install (malicious versions 99.13.9, 99.31.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in business-data (npm)

MAL-2026-2737

Immediate action

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

npm uninstall business-data

What this malware does

The package business-data was found to contain malicious code.

Malicious versions

2 flagged

99.13.999.31.9

Indicators of compromise (SHA-256)

423141680b73c8e469f564ecc47790d63a66d2a9c99a32b0b9a5cbb3c5a188bd

0cf2ae4dcc02b71af0e0b806893b36de2c89d775c82272eea71c6d87ac37f1f3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for business-data (2 malicious versions).
If you installed it — respond
Remove business-data 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 business-data 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. business-data on npm has been identified as a malicious package (versions 99.13.9, 99.31.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01903

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks business-data-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