Which versions of onb-enrichment are malicious?

The following npm versions of onb-enrichment are flagged malicious: 3.99.99. Treat any of these as compromised.

How do I remediate onb-enrichment if I installed it?

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

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

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

Search your lockfiles and build artifacts for onb-enrichment (version 3.99.99).

Malicious package

onb-enrichmentnpm

Advisory published Mar 24, 2026Updated Apr 7, 2026

onb-enrichment is a confirmed malicious npm package (MAL-2026-2381) that executes malicious code on install (malicious version 3.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in onb-enrichment (npm)

MAL-2026-2381

Immediate action

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

npm uninstall onb-enrichment

What this malware does

The package onb-enrichment was found to contain malicious code.

Malicious versions

1 flagged

3.99.99

Indicators of compromise (SHA-256)

f56c5c82bfe9ab245e997b264389af64ad472d57e920e4dd71a7f644cabe5734

8ce0c5fb4cfe81321cd7c89306b2049a57e60bffd84f128d9f72f11aaa4d0223

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01802

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks onb-enrichment-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