Which versions of adobe-alloy-mini-site are malicious?

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

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

adobe-alloy-mini-site 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-mini-site — how do I know if it already compromised me?

If adobe-alloy-mini-site 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 adobe-alloy-mini-site part of a known attack campaign?

Yes — adobe-alloy-mini-site is associated with the RLMA-2025-04913, RLUA-2025-05677 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-mini-site 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 adobe-alloy-mini-site (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging adobe-alloy-mini-site across your stack and pipelines.

Malicious package

adobe-alloy-mini-sitenpm

adobe-alloy-mini-site is a confirmed malicious npm package (MAL-2025-47577) 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-mini-site (npm)

MAL-2025-47577

Immediate action

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

npm uninstall adobe-alloy-mini-site

What this malware does

The package adobe-alloy-mini-site 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)

8c95a9e2db5b57105d60395cd2856d366b31bf3e1fab72926d75505efa6abcd7

d728d9b200c3b58899afcf6beb561ec60882028a3368ade745710195d969df22

b7402ea0fa9b179ac4a510804bb7dc1133bd8ae6d35c95d7f08f72655afc78c9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for adobe-alloy-mini-site (version 99.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging adobe-alloy-mini-site across your stack and pipelines.
If you installed it — respond
adobe-alloy-mini-site 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-mini-site 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 adobe-alloy-mini-site 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. adobe-alloy-mini-site 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-04913RLUA-2025-05677

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks adobe-alloy-mini-site-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