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

@rsgweb/locale-toolsnpm

Malicious code in @rsgweb/locale-tools (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-786
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @rsgweb/locale-tools

What this malware does

The package @rsgweb/locale-tools 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.

The OpenSSF Package Analysis project identified '@rsgweb/locale-tools' @ 136.3.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
136.3.1

Indicators of compromise (SHA-256)

132ad2428e5535d1cd2453628af25f871f9ec7a10d66e074cfe519247a760e9b
5bebf7aabcf0d6fa5effca3aac94a5793c1b000b824b24d33367d9b517e4b174
6b1882e2ffa769f9383127f2bfc582935b3bb1145e172eb6941a0276989a983f

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 @rsgweb/locale-tools (version 136.3.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @rsgweb/locale-tools across your stack and pipelines.

  2. If you installed it — respond

    Remove @rsgweb/locale-tools 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 @rsgweb/locale-tools 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 @rsgweb/locale-tools 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. @rsgweb/locale-tools on npm has been identified as a malicious package (version 136.3.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-45p4-h5vh-f9rw

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @rsgweb/locale-tools-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.

@rsgweb/locale-tools (npm) malicious package — MAL-2026-786 | O3 Security