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

jito-sub-aes-ipherivnpm

jito-sub-aes-ipheriv is a confirmed malicious npm package (MAL-2025-47979) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jito-sub-aes-ipheriv (npm)

MAL-2025-47979
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall jito-sub-aes-ipheriv

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

4 flagged
1.0.11.0.21.0.31.0.4

Indicators of compromise (SHA-256)

103b0ca3b2a6d09bab1b2b0a19d08540d01dfbfe07e7eba218427c25239cfbc1
0356efa74b7705cfc17663b357a14e8ceb645adfcffa633689d66359002d05af
155dbe19f36bcdc6223c8a8e9368edc5d508796780fb2bbf056631a8080e64a8
c16307ce8452997518f0aab583a0c98cd26ff6699e61c69f1cee6bb8023c90c4

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 jito-sub-aes-ipheriv (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jito-sub-aes-ipheriv across your stack and pipelines.

  2. If you installed it — respond

    Remove jito-sub-aes-ipheriv 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 jito-sub-aes-ipheriv 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 jito-sub-aes-ipheriv 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. jito-sub-aes-ipheriv on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3g54-9gjh-m8rjRLMA-2025-05403RLUA-2025-05819RLUA-2026-05123

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks jito-sub-aes-ipheriv-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

jito-sub-aes-ipheriv (npm) malicious package — MAL-2025-47979 | O3 Security