Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

sap-code-style-guidesnpm

Malicious code in sap-code-style-guides (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-835
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sap-code-style-guides

What this malware does

The package sap-code-style-guides 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

5 flagged
1.1.099.99.9999.99.10099.99.10199.99.102

Indicators of compromise (SHA-256)

044191908e0ca5957496df2ee5bb002c75cbf76fb90abd3240844b88c906804d
13203a88392c91986f587e28ca25120b54f0c4d4ee5dd2c330c2bbbe6243203a
712a9d6ba01c7dc6160c77d40a9ea1a1c847be4d1cf3b06642b1d8f99e65ced6

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for sap-code-style-guides (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sap-code-style-guides across your stack and pipelines.

  2. If you installed it — respond

    Remove sap-code-style-guides 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 sap-code-style-guides 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.

  4. How O3 protects you

    O3 blocks sap-code-style-guides 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. sap-code-style-guides on npm has been identified as a malicious package (versions 1.1.0, 99.99.99, 99.99.100, 99.99.101, 99.99.102 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-6pjr-w5hp-m7pjRLMA-2026-01547

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks sap-code-style-guides-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.

sap-code-style-guides (npm) malicious package — MAL-2026-835 | O3 Security