Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Part of a larger attack: @operato published 13 malicious packages. See the full campaign →
Malicious package

@operato/i18nnpm

@operato/i18n is a confirmed malicious npm package (MAL-2025-47257) that steals credentials and exfiltrates sensitive data (malicious versions 9.0.35, 9.0.36, 9.0.37). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @operato/i18n (npm)

MAL-2025-47257
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @operato/i18n

What this malware does

The package was compromised and malicious code added.

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.

This package was compromised by the Shai-Hulud NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub before propogating itself to NPM packages the user owns.

Malicious versions

3 flagged
9.0.359.0.369.0.37

Indicators of compromise (SHA-256)

fc67f45593512ec564f71036ae8e4d33dabfb3b45021a37f253ca8fb76d2027f
8b429a40c36ae09cd05605d5fd0a0dc993edb261b9fd25628b6eaef1b27c9de5
c15467f134a1515b4dbb2fa40a56bf3f91671ccf7ed171905841fa3021656584
d9e914fd4230c562e1391e077b5928c755a7f3c70f9402a45bc1c95c67a60a24

Detection & response playbook

Credential / info stealer
  1. Find it

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

  2. If you installed it — respond

    @operato/i18n is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @operato/i18n 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 @operato/i18n 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. @operato/i18n on npm has been identified as a malicious package (versions 9.0.35, 9.0.36, 9.0.37 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vc38-9887-355j

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @operato/i18n-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@operato/i18n (npm) malicious package — MAL-2025-47257 | O3 Security