Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

ab-test-wordpressnpm

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

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for ab-test-wordpress (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-test-wordpress across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If ab-test-wordpress 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.

  4. How O3 protects you

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

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.

Explore

ab-test-wordpress (npm) malicious package — MAL-2025-48477 | O3 Security