Which versions of sdbao-content-report are malicious?

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

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

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

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

Yes — sdbao-content-report is associated with the GHSA-xqgm-344j-vx3r, RLMA-2025-06470, RLUA-2026-01553 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-report 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-report (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-report across your stack and pipelines.

Malicious package

sdbao-content-reportnpm

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

MAL-2025-192564

Immediate action

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

npm uninstall sdbao-content-report

What this malware does

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

7ff04db3a451220da18f6f8e689b6a54e2a2339da4bc944e75cca3c8742ede7e

352174ed8ad21b72357fc69c51e395ee7b1ceb75b55603d205bdc8280dfc00b1

b76a249515baf81a80b051dc0b9c9bf6c9f4189f17c0962cbe1bf851da527468

a2733dabe11d6288ac0cabdd1dff5c6c2e805d6f43be34332c3a5d5251b1688d

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-report (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-report across your stack and pipelines.
If you installed it — respond
Remove sdbao-content-report 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-report 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-report 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-report 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-xqgm-344j-vx3rRLMA-2025-06470RLUA-2026-01553

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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