Which versions of apex-connector are malicious?

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

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

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

If apex-connector 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-connector across my projects, lockfiles, and CI pipelines?

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

Malicious package

apex-connectornpm

Advisory published May 16, 2026Updated May 19, 2026

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

MAL-2026-3816

Immediate action

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

npm uninstall apex-connector

What this malware does

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

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

f91ca1cc1f5026a4e28e4b9ac50953bd3d77ef888955c9ef5328bfd898fe1640

33a26a7f829a26ef83ab119b6d61de6109d553f0b34432bf1efb37d5f56f4064

Detection & response playbook

Malicious package

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