Which versions of sdbao-content-sems are malicious?

The following npm versions of sdbao-content-sems are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate sdbao-content-sems if I installed it?

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

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

Yes — sdbao-content-sems is associated with the GHSA-m87p-xpm6-rjwq, RLMA-2025-06471, RLUA-2026-01554 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 sdbao-content-sems 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 sdbao-content-sems (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 sdbao-content-sems across your stack and pipelines.

Malicious package

sdbao-content-semsnpm

Malicious code in sdbao-content-sems (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-192565

Immediate action

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

npm uninstall sdbao-content-sems

What this malware does

The package sdbao-content-sems 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)

64d83cb336bfeb0a0ebd8fa6284e9d4459a69cce447f1cee69bfe3979cf7c481

050ceeb8145a6cac66b0539a7be8d50c66979cd72b54055f3c49c0c40823fd6b

28f58f6780cbfa6c3b9102cc0cab95fb718df39a76dc473ca99b888ecf84ca3f

48a418636313971541a6de4298a9d668805e9cf1d53a9059746faaa37ede890d

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 sdbao-content-sems (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 sdbao-content-sems across your stack and pipelines.
If you installed it — respond
Remove sdbao-content-sems 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 sdbao-content-sems 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 sdbao-content-sems 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. sdbao-content-sems 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-m87p-xpm6-rjwqRLMA-2025-06471RLUA-2026-01554

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks sdbao-content-sems-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