Which versions of omnicore-ds2-sdk2 are malicious?

The following npm versions of omnicore-ds2-sdk2 are flagged malicious: 9.9.1, 99.9.3. Treat any of these as compromised.

How do I remediate omnicore-ds2-sdk2 if I installed it?

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

If omnicore-ds2-sdk2 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 omnicore-ds2-sdk2 part of a known attack campaign?

Yes — omnicore-ds2-sdk2 is associated with the RLMA-2026-01472 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 omnicore-ds2-sdk2 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for omnicore-ds2-sdk2 (2 malicious versions).

Malicious package

omnicore-ds2-sdk2npm

Advisory published Jan 16, 2026Updated Mar 19, 2026

omnicore-ds2-sdk2 is a confirmed malicious npm package (MAL-2026-298) that executes malicious code on install (malicious versions 9.9.1, 99.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in omnicore-ds2-sdk2 (npm)

MAL-2026-298

Immediate action

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

npm uninstall omnicore-ds2-sdk2

What this malware does

The package omnicore-ds2-sdk2 was found to contain malicious code.

Malicious versions

2 flagged

9.9.199.9.3

Indicators of compromise (SHA-256)

26e1c62468ce0da7fc1beb34de16d8faa8633411ce4217f2d4e6b6bf3fc92a53

9aace5178c965d1851253ee3737aebf30bd973d2e9b4ac83f0c69511c02918ac

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01472

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks omnicore-ds2-sdk2-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