Which versions of spstargm are malicious?

The following npm versions of spstargm are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate spstargm if I installed it?

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

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

Yes — spstargm is associated with the GHSA-x24f-q36q-6pcj 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 spstargm 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 spstargm (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spstargm across your stack and pipelines.

Malicious package

spstargmnpm

Malicious code in spstargm (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1969

Immediate action

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

npm uninstall spstargm

What this malware does

The package spstargm 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

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

a0415f3c475983a53adb25756b7fd123d025c7be9670499938f81de0229f596e

54ce1a8a7d00ca1aef6f9b8efb51402365637ca06d3d60ac779221ed3c0827d9

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 spstargm (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spstargm across your stack and pipelines.
If you installed it — respond
Remove spstargm 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 spstargm 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 spstargm 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. spstargm on npm has been identified as a malicious package (versions 1.0.0, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x24f-q36q-6pcj

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks spstargm-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