Which versions of ok-jest-config are malicious?

The following npm versions of ok-jest-config are flagged malicious: 5.0.0, 5.1.0. Treat any of these as compromised.

How do I remediate ok-jest-config if I installed it?

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

If ok-jest-config 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 ok-jest-config part of a known attack campaign?

Yes — ok-jest-config is associated with the RLMA-2026-01471 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 ok-jest-config across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ok-jest-config (2 malicious versions).

Malicious package

ok-jest-confignpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

ok-jest-config is a confirmed malicious npm package (MAL-2026-1806) that executes malicious code on install (malicious versions 5.0.0, 5.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ok-jest-config (npm)

MAL-2026-1806

Immediate action

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

npm uninstall ok-jest-config

What this malware does

The package ok-jest-config was found to contain malicious code.

Malicious versions

2 flagged

5.0.05.1.0

Indicators of compromise (SHA-256)

a740419cd61be3384a859e5b25b1db0de8b0cabb919e979386ada2a7c2a735ec

325c8c29810fe4350343efe3d17484a0cd3f9d3617ff312bae86468449c95e14

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01471

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ok-jest-config-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