Which versions of access-worker-test are malicious?

The following npm versions of access-worker-test are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate access-worker-test if I installed it?

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

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

Yes — access-worker-test is associated with the RLMA-2026-01875 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 access-worker-test across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for access-worker-test (version 0.0.1).

Malicious package

access-worker-testnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

access-worker-test is a confirmed malicious npm package (MAL-2026-2721) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in access-worker-test (npm)

MAL-2026-2721

Immediate action

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

npm uninstall access-worker-test

What this malware does

The package access-worker-test was found to contain malicious code.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d8ce16bfec048001e855888487ad2e6e4304b85fed5db7bcfa5be47436193d9a

90ffaa308018be94514f70476e1756144af41a3f03028aa640c8ab24c7edfcc0

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-01875

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks access-worker-test-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