Which versions of ab-test-wordpress are malicious?

The following npm versions of ab-test-wordpress are flagged malicious: 1.18.3. Treat any of these as compromised.

How do I remediate ab-test-wordpress if I installed it?

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

If ab-test-wordpress 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 ab-test-wordpress part of a known attack campaign?

Yes — ab-test-wordpress is associated with the RLMA-2025-05673, RLUA-2026-10673 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 ab-test-wordpress across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ab-test-wordpress (version 1.18.3).

Malicious package

ab-test-wordpressnpm

Advisory published Oct 14, 2025Updated Sep 24, 2026

ab-test-wordpress is a confirmed malicious npm package (MAL-2025-48477) that executes malicious code on install (malicious version 1.18.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ab-test-wordpress (npm)

MAL-2025-48477

Immediate action

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

npm uninstall ab-test-wordpress

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.18.3

Indicators of compromise (SHA-256)

b96993337f78d2adb4e1788fc4e5f759923215af6d8bedb381ee56ee97e991a9

9b6ab6220df7616416f5af59281dc848ce48130e26ed7bff94e49fb1febd7fc0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-05673RLUA-2026-10673

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ab-test-wordpress-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