Which versions of sparkling-router are malicious?

The following npm versions of sparkling-router are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate sparkling-router if I installed it?

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

If sparkling-router was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is sparkling-router part of a known attack campaign?

Yes — sparkling-router is associated with the GHSA-rcjf-9p8h-7q5w, RLMA-2026-01586 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 sparkling-router across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sparkling-router (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sparkling-router across your stack and pipelines.

Malicious package

sparkling-routernpm

Malicious code in sparkling-router (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-311

Immediate action

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

npm uninstall sparkling-router

What this malware does

The package sparkling-router 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.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

22829b6f6507a82b0a8acae51ea2b4cc5034afde231740f3eaede5e0af3a0fac

6e84c7e51a68544e8af8935aa539926a2bc3d269e42c78c99a3765e76c54770f

2a1c87232c031e53b3e4b944f5094331bf833cad71d25e4fb1cc411e09cf1ade

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sparkling-router (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sparkling-router across your stack and pipelines.
If you installed it — respond
Remove sparkling-router 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 sparkling-router was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks sparkling-router before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. sparkling-router on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rcjf-9p8h-7q5wRLMA-2026-01586

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sparkling-router-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