Which versions of aes-core-valid-ipherv are malicious?

The following npm versions of aes-core-valid-ipherv are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate aes-core-valid-ipherv if I installed it?

Remove aes-core-valid-ipherv 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-core-valid-ipherv — how do I know if it already compromised me?

If aes-core-valid-ipherv 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-core-valid-ipherv part of a known attack campaign?

Yes — aes-core-valid-ipherv is associated with the GHSA-f8qj-79cq-rg8h, RLMA-2025-05679, RLUA-2025-06055 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-core-valid-ipherv 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-core-valid-ipherv (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aes-core-valid-ipherv across your stack and pipelines.

Malicious package

aes-core-valid-iphervnpm

Malicious code in aes-core-valid-ipherv (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-149905

Immediate action

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

npm uninstall aes-core-valid-ipherv

What this malware does

The package aes-core-valid-ipherv 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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

2489309aeb6200e7b5ec1fa1bb5f8a5f92e087066b0fedc4dde335428ee84736

c4b3e5a270d63d751fe142a9d81d59870ee3c9bbe18403a4da5fbff3c5cce2b8

fb10833e8d80ade903f9212e7c7e58f75481ad74d255b938cee130dd0c3d5ded

c2a65b94842c9888180ef39110c0d1b275416c7bc91c1b5e6f2f33030180ab57

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-core-valid-ipherv (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aes-core-valid-ipherv across your stack and pipelines.
If you installed it — respond
Remove aes-core-valid-ipherv 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-core-valid-ipherv 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-core-valid-ipherv 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-core-valid-ipherv on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-f8qj-79cq-rg8hRLMA-2025-05679RLUA-2025-06055

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks aes-core-valid-ipherv-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