Which versions of sd-skbms are malicious?

The following npm versions of sd-skbms are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate sd-skbms if I installed it?

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

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

Yes — sd-skbms is associated with the GHSA-ww9c-3crf-rqcp, RLMA-2025-06469, RLUA-2026-01552 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 sd-skbms 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 sd-skbms (version 999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sd-skbms across your stack and pipelines.

Malicious package

sd-skbmsnpm

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

MAL-2025-192577

Immediate action

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

npm uninstall sd-skbms

What this malware does

The package sd-skbms 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

999.0.0

Indicators of compromise (SHA-256)

9cf1a086ee102f5bbaa7b18b6512f3457de46a88a240dd3acda1bcfffe28f58c

37d7af5c9829af6d62bf3237e014e1a9a6cbcd30be7eb56096229f226428f607

bc7e62a41f59ebec3cf79da6d18fbfadc09e89d93407926aeff9ffad7495c1f6

e7d55a6b52f4c6489085b54addbc36aad736d36e953ad9e0f4bf325575f8308d

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

Campaign

GHSA-ww9c-3crf-rqcpRLMA-2025-06469RLUA-2026-01552

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sd-skbms-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