NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@bscom/stylingnpm

Advisory published Updated

@bscom/styling is a confirmed malicious npm package (MAL-2026-6605) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bscom/styling (npm)

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
3b7572e9e7d0032944e45514273e8e4b776d6ae7c60ea9cd4553e5e5a390ab5d

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @bscom/styling (version 99.9.1).

  2. 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.

  3. Did it already run?

    If @bscom/styling was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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-04694RLUA-2026-05402

References

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.

Explore

@bscom/styling (npm) malicious package — MAL-2026-6605 | O3 Security