What does the optly malware do?

The package optly was found to contain malicious code. The OpenSSF Package Analysis project identified 'optly' @ 90.6.6 (npm) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of optly are malicious?

The following npm versions of optly are flagged malicious: 90.6.6. Treat any of these as compromised.

How do I remediate optly if I installed it?

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

If optly 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.

How do I find optly across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for optly (version 90.6.6).

Malicious package

optlynpm

Advisory published Nov 21, 2025Updated Nov 24, 2025

optly is a confirmed malicious npm package (MAL-2025-190600) that executes malicious code on install (malicious version 90.6.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in optly (npm)

MAL-2025-190600

Immediate action

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

npm uninstall optly

What this malware does

The package optly was found to contain malicious code.

The OpenSSF Package Analysis project identified 'optly' @ 90.6.6 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

90.6.6

Indicators of compromise (SHA-256)

e70192025ea0e8c030d0adbe15f6c3272271f3b25cb13eedfb8136da48c9a29a

e0772e230f188de88a82becfa6493f2c39c36e63290339595308366a84154a56

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database