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

rtms-managernpm

Malicious code in rtms-manager (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2862
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rtms-manager

What this malware does

The package rtms-manager was found to contain malicious code.

The OpenSSF Package Analysis project identified 'rtms-manager' @ 1.2.0 (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

2 flagged
1.2.01.4.0

Indicators of compromise (SHA-256)

d50c578dddb4a0cd216dd21c4432a54846daef2a4c41bd80aef2ca6a983dacd5
c18da37bf0615d0c7dceb6be7eb89956f39de56bbc90f65d9398fbfb3f9455dc
ba81d4885b3bbde680dc475922b0b6baf7bc02d50432d9addc5278b3b4d4efce

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 rtms-manager (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging rtms-manager across your stack and pipelines.

  2. If you installed it — respond

    Remove rtms-manager 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 rtms-manager 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 rtms-manager 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. rtms-manager on npm has been identified as a malicious package (versions 1.2.0, 1.4.0 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 rtms-manager-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.

rtms-manager (npm) malicious package — MAL-2026-2862 | O3 Security