Which versions of sb_wm_integrator are malicious?

The following npm versions of sb_wm_integrator are flagged malicious: 10.0.33. Treat any of these as compromised.

How do I remediate sb_wm_integrator if I installed it?

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

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

Yes — sb_wm_integrator is associated with the RLMA-2025-05941 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 sb_wm_integrator 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 sb_wm_integrator (version 10.0.33). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sb_wm_integrator across your stack and pipelines.

Malicious package

sb_wm_integratornpm

sb_wm_integrator is a confirmed malicious npm package (MAL-2025-48505) that executes malicious code on install (malicious version 10.0.33). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in sb_wm_integrator (npm)

MAL-2025-48505

Immediate action

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

npm uninstall sb_wm_integrator

What this malware does

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

10.0.33

Indicators of compromise (SHA-256)

df795196cbbba07325713283aff1e858f8d35770cf7d06215b3fc05f86cc383f

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

Campaign

RLMA-2025-05941

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database