NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

apcyber-test-packagenpm

Advisory published Updated

apcyber-test-package is a confirmed malicious npm package (MAL-2026-3304) that executes malicious code on install (malicious versions 1.0.0, 99.99.99, 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in apcyber-test-package (npm)

MAL-2026-3304
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apcyber-test-package

What this malware does

The package apcyber-test-package was found to contain malicious code.

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.

The OpenSSF Package Analysis project identified 'apcyber-test-package' @ 99.99.99 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.0.099.99.99100.0.0

Indicators of compromise (SHA-256)

e6a50b18823ef5c1ec2bac66ebde8c45a5b1c0601c2a25f7d9a5ca2ee9de6a4e
9469480038fbb55dc92d08344eac146ece79d19900717a422c37e82b65c22025
4386e2b20fb74fe5b131a23550b9550b4539a3f79056ea8ad08f502453409737
2cb5a2d786ce484c868a2ea24e4e29c633d50cae2b307ae8ba626b0a2b41560e
bdefe5c7ed4fcfb1777a0b20c1309e6ad457fde521b11c90e69f5044b7aa0278

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for apcyber-test-package (3 malicious versions).

  2. If you installed it — respond

    Remove apcyber-test-package 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 apcyber-test-package 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. apcyber-test-package on npm has been identified as a malicious package (versions 1.0.0, 99.99.99, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-xr6f-x85p-m7ffRLMA-2026-04928

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks apcyber-test-package-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

apcyber-test-package (npm) malicious package — MAL-2026-3304 | O3 Security