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

rt-footernpm

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

MAL-2026-138
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rt-footer

What this malware does

The package rt-footer was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

d3f499cb715f4d755c0be8690d154c1da2a95c1195bff56c58d5967d2b680e6e
843ded25c4705270d68a2528b9a2aadd0755998b2880686a4ea7ad2d777a1235

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

  2. If you installed it — respond

    Remove rt-footer 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 rt-footer 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 rt-footer 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. rt-footer on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pm9v-3jmc-jh7g

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rt-footer-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.

rt-footer (npm) malicious package — MAL-2026-138 | O3 Security