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

apexpro-nodenpm

Advisory published Updated

apexpro-node is a confirmed malicious npm package (MAL-2026-3819) that executes malicious code on install (malicious version 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in apexpro-node (npm)

MAL-2026-3819
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall apexpro-node

What this malware does

The package apexpro-node 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 'apexpro-node' @ 1.0.4 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged
1.0.4

Indicators of compromise (SHA-256)

b056a76184846075482782159adbcefdb93dfb83739ef6e4713b48fc1492419d
95c8a3b29ed31b909fa4a13a8b310c4cee8f115748f7b708aeab52ab2b66fdbb
e4cc91e23bb614febd12cef6d21d4456fb9cfa198c2aa76215d1b38dd820d9b4

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for apexpro-node (version 1.0.4).

  2. If you installed it — respond

    Remove apexpro-node 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 apexpro-node 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. apexpro-node on npm has been identified as a malicious package (version 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-m598-5772-88pg

References

Credits

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

Detect & block this

O3 blocks apexpro-node-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

apexpro-node (npm) malicious package — MAL-2026-3819 | O3 Security