Which versions of options-msg are malicious?

The following npm versions of options-msg are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5. Treat any of these as compromised.

How do I remediate options-msg if I installed it?

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

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

Yes — options-msg is associated with the RLMA-2026-05196, RLUA-2026-06357 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 options-msg across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for options-msg (6 malicious versions).

Malicious package

options-msgnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

options-msg is a confirmed malicious npm package (MAL-2026-7332) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in options-msg (npm)

MAL-2026-7332

Immediate action

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

npm uninstall options-msg

Malicious versions

6 flagged

1.0.01.0.11.0.21.0.31.0.41.0.5

Indicators of compromise (SHA-256)

cccc5db0ed5b00d861cc6bd2856a3f0c06f1c92b9b4c482f01ff28da4ee7f375

8c7204a690a6c29ca7250ca4114898d49094b6fd429443ca4edf54cf697cd6a3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for options-msg (6 malicious versions).
If you installed it — respond
Remove options-msg 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 options-msg 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. options-msg on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05196RLUA-2026-06357

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks options-msg-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