Which versions of otetotvot are malicious?

The following npm versions of otetotvot are flagged malicious: 0.30.1, 0.30.2. Treat any of these as compromised.

How do I remediate otetotvot if I installed it?

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

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

Yes — otetotvot is associated with the RLMA-2025-06441 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 otetotvot across my projects, lockfiles, and CI pipelines?

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

Malicious package

otetotvotnpm

Advisory published Nov 9, 2025Updated Dec 24, 2025

otetotvot is a confirmed malicious npm package (MAL-2025-49428) that executes malicious code on install (malicious versions 0.30.1, 0.30.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in otetotvot (npm)

MAL-2025-49428

Immediate action

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

npm uninstall otetotvot

What this malware does

The package otetotvot was found to contain malicious code.

Malicious versions

2 flagged

0.30.10.30.2

Indicators of compromise (SHA-256)

0d851ffe3957cba1f82becabf9c93f7d6aec17d686a638291f0748564f9f846c

3c42057f363bbe684cd66958fec7c0368772209fac0c3d46cbc2d45a5bd9bb34

Detection & response playbook

Malicious package

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

Campaign

RLMA-2025-06441

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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