Which versions of spark-common are malicious?

The following npm versions of spark-common are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate spark-common if I installed it?

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

If spark-common 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 spark-common part of a known attack campaign?

Yes — spark-common is associated with the RLMA-2026-10789 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 spark-common across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spark-common (version 1.0.0).

Malicious package

spark-commonnpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

spark-common is a confirmed malicious npm package (MAL-2026-16537) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spark-common (npm)

MAL-2026-16537

Immediate action

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

npm uninstall spark-common

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

7f859dcd58786e3a36584567617a50a9ff8ed444421c6828e42b1bc96f626149

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10789

Credits

ReversingLabs · finder

Detect & block this

O3 blocks spark-common-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