Which versions of adobe-alloy are malicious?

The following npm versions of adobe-alloy are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate adobe-alloy if I installed it?

adobe-alloy 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.

I already installed adobe-alloy — how do I know if it already compromised me?

If adobe-alloy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is adobe-alloy part of a known attack campaign?

Yes — adobe-alloy is associated with the RLMA-2025-04912, RLUA-2025-05676 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 adobe-alloy across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for adobe-alloy (version 99.0.0).

Malicious package

adobe-alloynpm

Advisory published Sep 25, 2025Updated Dec 2, 2025

adobe-alloy is a confirmed malicious npm package (MAL-2025-47576) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adobe-alloy (npm)

MAL-2025-47576

Immediate action

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

npm uninstall adobe-alloy

What this malware does

The package adobe-alloy was found to contain malicious code.

This package installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

4765e309daa5f180841a5358f3143369c47386b1af23cf68ffe9083cc39b5758

a8e952541082c8bec5f3b5c23a250995aa6d04b35925087502b6ed7100760d27

e2bd3bc693b63ef6b433b2ac7af83df466672c727794d9c4015c7c6a40539870

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for adobe-alloy (version 99.0.0).
If you installed it — respond
adobe-alloy 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.
Did it already run?
If adobe-alloy was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. adobe-alloy on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04912RLUA-2025-05676

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database