Which versions of ab-testing-for-wp are malicious?

The following npm versions of ab-testing-for-wp are flagged malicious: 1.18.3. Treat any of these as compromised.

How do I remediate ab-testing-for-wp if I installed it?

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

If ab-testing-for-wp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is ab-testing-for-wp part of a known attack campaign?

Yes — ab-testing-for-wp is associated with the GHSA-q4jh-hrp9-4qc5, RLMA-2025-05674 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-testing-for-wp across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ab-testing-for-wp (version 1.18.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ab-testing-for-wp across your stack and pipelines.

Malicious package

ab-testing-for-wpnpm

ab-testing-for-wp is a confirmed malicious npm package (MAL-2025-48478) 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-testing-for-wp (npm)

MAL-2025-48478

Immediate action

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

npm uninstall ab-testing-for-wp

What this malware does

The package communicates with a domain associated with malicious activity.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.18.3

Indicators of compromise (SHA-256)

0b0f0c139e34ac20e878e9cfdbe5c7a6b664b8cdd4144f1df0bc2ffc948ee661

697f4649cb5a474ef8ee3b506127c7d40c9abd332cb81799e6de3a1daa40f5ec

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ab-testing-for-wp (version 1.18.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ab-testing-for-wp across your stack and pipelines.
If you installed it — respond
Remove ab-testing-for-wp 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-testing-for-wp was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks ab-testing-for-wp before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. ab-testing-for-wp 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

GHSA-q4jh-hrp9-4qc5RLMA-2025-05674

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ab-testing-for-wp-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