Which versions of apex-trading are malicious?

The following npm versions of apex-trading are flagged malicious: 1.0.4. Treat any of these as compromised.

How do I remediate apex-trading if I installed it?

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

If apex-trading 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.

How do I find apex-trading across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for apex-trading (version 1.0.4).

Malicious package

apex-tradingnpm

Advisory published May 16, 2026Updated May 19, 2026

apex-trading is a confirmed malicious npm package (MAL-2026-3817) 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 apex-trading (npm)

MAL-2026-3817

Immediate action

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

npm uninstall apex-trading

What this malware does

The package apex-trading was found to contain malicious code.

The OpenSSF Package Analysis project identified 'apex-trading' @ 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)

faf0dac877583a2ef1970711afb8c0555a7bac157bb526e9ebb66fb1393ecb8c

7cf744353f06f389c92cd15c56bf0ec7d29860e8af7c9618413cf65e455428eb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for apex-trading (version 1.0.4).
If you installed it — respond
Remove apex-trading 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 apex-trading 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. apex-trading 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.

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks apex-trading-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