Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

otetotvotnpm

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
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for otetotvot (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging otetotvot across your stack and pipelines.

  2. 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.

  3. Did it already run?

    If otetotvot was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks otetotvot before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

Explore

otetotvot (npm) malicious package — MAL-2025-49428 | O3 Security