Which versions of aesdecryptor are malicious?

The following npm versions of aesdecryptor are flagged malicious: 1.0.0, 1.1.0. Treat any of these as compromised.

How do I remediate aesdecryptor if I installed it?

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

If aesdecryptor 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 aesdecryptor part of a known attack campaign?

Yes — aesdecryptor is associated with the GHSA-87mr-4wrw-h27g, RLMA-2026-01710, RLUA-2026-01879 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 aesdecryptor 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 aesdecryptor (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aesdecryptor across your stack and pipelines.

Malicious package

aesdecryptornpm

Malicious code in aesdecryptor (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1473

Immediate action

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

npm uninstall aesdecryptor

What this malware does

The package aesdecryptor 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

2 flagged

1.0.01.1.0

Indicators of compromise (SHA-256)

67de86e4e1b93130bb4f76480f236f202b1f257067eaf1ca02d3c565c2fc8edb

2ac66c3676fdc79338dd38b32cacdd68d6f86e097c163eb1e8e4bd556de82c69

7b019558e753b9e5f3f869d6c77908531e9bed4bbee768334ce378b0d48ae1ab

fea77bfd122545c203a46284cc51ca9a5b11c46756b7c3e5207d3ff79500c039

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

Campaign

GHSA-87mr-4wrw-h27gRLMA-2026-01710RLUA-2026-01879

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks aesdecryptor-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