Which versions of ibotta-ts are malicious?

The following npm versions of ibotta-ts are flagged malicious: 45.0.0. Treat any of these as compromised.

How do I remediate ibotta-ts if I installed it?

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

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

Yes — ibotta-ts is associated with the RLMA-2026-05111, RLUA-2026-06278 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 ibotta-ts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ibotta-ts (version 45.0.0).

Malicious package

ibotta-tsnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

ibotta-ts is a confirmed malicious npm package (MAL-2026-7297) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ibotta-ts (npm)

MAL-2026-7297

Immediate action

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

npm uninstall ibotta-ts

Malicious versions

1 flagged

45.0.0

Indicators of compromise (SHA-256)

d290e9637ec8da37361d4c96236139f5f901311f5253318231feb6f5a726c733

a5861dd4f63430a012fb241135c91b38c3be82f93b814426641ac14255539cc9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05111RLUA-2026-06278

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ibotta-ts-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