Which versions of aes-create-ipheriv are malicious?

The following npm versions of aes-create-ipheriv are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate aes-create-ipheriv if I installed it?

Remove aes-create-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.

I already installed aes-create-ipheriv — how do I know if it already compromised me?

If aes-create-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.

Is aes-create-ipheriv part of a known attack campaign?

Yes — aes-create-ipheriv is associated with the GHSA-vfgx-78gh-pprh, RLMA-2025-05279, RLUA-2025-05680, RLUA-2026-04824 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find aes-create-ipheriv across my projects, lockfiles, and CI pipelines?

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

Malicious package

aes-create-ipherivnpm

Malicious code in aes-create-ipheriv (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-47972

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall aes-create-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

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

32024f762cae5f727853e7d6e07ee5012a1b440d859182a62be6123eb638e873

01b0feb01efc627163ffed6c5468ab3bf02c62c191df1c8294b2276fb6d04d8b

55c4083f4d299ea9af3c47be7b5a18851e0de79e2974ec851b3a60030a37b95e

c322d68ae4148a9c9b4e80e8b64ab890da7c0a819335bfb2c9363e7d23ea4c85

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aes-create-ipheriv (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aes-create-ipheriv across your stack and pipelines.
If you installed it — respond
Remove aes-create-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.
Did it already run?
If aes-create-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.
How O3 protects you
O3 blocks aes-create-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. aes-create-ipheriv on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vfgx-78gh-pprhRLMA-2025-05279RLUA-2025-05680RLUA-2026-04824

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks aes-create-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.

Malware detection Runtime egress monitoring