Which versions of @bscom/styling are malicious?

The following npm versions of @bscom/styling are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @bscom/styling if I installed it?

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

If @bscom/styling 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 @bscom/styling part of a known attack campaign?

Yes — @bscom/styling is associated with the GHSA-29c6-c7cm-r8ch, RLMA-2026-04694 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 @bscom/styling 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 @bscom/styling (version 99.9.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @bscom/styling across your stack and pipelines.

Malicious package

@bscom/stylingnpm

Malicious code in @bscom/styling (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6605

Immediate action

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

npm uninstall @bscom/styling

What this malware does

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

99.9.1

Indicators of compromise (SHA-256)

3b4a6eb2b93e7ac0b6e45f2cc44f23127ef61b7d605b6c64f6bcbc58bdbe4543

ac011052ea4439d8445f0f459fe260e3c1db822a90792c17d68c6e9650e9bc99

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

Campaign

GHSA-29c6-c7cm-r8chRLMA-2026-04694

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @bscom/styling-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