Which versions of adorn are malicious?

The following npm versions of adorn are flagged malicious: 0.1.0, 0.1.1. Treat any of these as compromised.

How do I remediate adorn if I installed it?

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

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

Yes — adorn is associated with the IN-MAL-2026-022327, IN-MAL-2026-022325 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 adorn across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for adorn (2 malicious versions).

Malicious package

adornnpm

Advisory published Aug 14, 2025Updated Oct 29, 2026

adorn is a confirmed malicious npm package (MAL-2025-14109) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in adorn (npm)

MAL-2025-14109

Immediate action

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

npm uninstall adorn

What this malware does

The package adorn was found to contain malicious code.

No install-time or import-time behavior of concern was observed in this package version. No lifecycle scripts performing network fetch or shell execution, no reads of installer secret paths (~/.aws, ~/.ssh, ~/.npmrc), no environment-variable scraping, no hardcoded attacker-controlled network destinations, no obfuscated payloads, and no silent-relay of caller-supplied data were identified.

Malicious versions

2 flagged

0.1.00.1.1

Indicators of compromise (SHA-256)

2d216a470f43a6fe1d8ad3afea30e01265f3b9d2c25fc6689e296ff7c817489a

e599d9e6ee3f5d7eb08a02b4dded1fe4a169ac106e857aeee90f7ad162a52913

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for adorn (2 malicious versions).
If you installed it — respond
adorn 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 adorn 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. adorn on npm has been identified as a malicious package (versions 0.1.0, 0.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022327IN-MAL-2026-022325

References

Credits

Amazon Inspector · finder

Detect & block this

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