Which versions of otomi-tasks are malicious?

The following npm versions of otomi-tasks are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate otomi-tasks if I installed it?

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

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

Yes — otomi-tasks is associated with the RLMA-2026-02015 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 otomi-tasks across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for otomi-tasks (version 9.9.9).

Malicious package

otomi-tasksnpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

otomi-tasks is a confirmed malicious npm package (MAL-2026-2789) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in otomi-tasks (npm)

MAL-2026-2789

Immediate action

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

npm uninstall otomi-tasks

What this malware does

The package otomi-tasks was found to contain malicious code.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

836f7349622a2c3c200e7f6054e7c810645d3f951092af6d5d5cf30c92fad69b

801ad983065c3d079ec114f2e5c5fc207a1903c098b383a2b049060d4d64f654

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02015

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks otomi-tasks-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