Which versions of omniauth-pro-sante-connect are malicious?

The following RubyGems versions of omniauth-pro-sante-connect are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, 0.1.8. Treat any of these as compromised.

How do I remediate omniauth-pro-sante-connect if I installed it?

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

If omniauth-pro-sante-connect 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 omniauth-pro-sante-connect part of a known attack campaign?

Yes — omniauth-pro-sante-connect is associated with the RLMA-2025-04303, RLUA-2025-06621 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 omniauth-pro-sante-connect across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for omniauth-pro-sante-connect (9 malicious versions).

Malicious package

omniauth-pro-sante-connectRubyGems

Advisory published Aug 28, 2025Updated Jul 23, 2026

omniauth-pro-sante-connect is a confirmed malicious RubyGems package (MAL-2025-41805) that executes malicious code on install (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in omniauth-pro-sante-connect (RubyGems)

MAL-2025-41805

Immediate action

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

gem uninstall omniauth-pro-sante-connect

Malicious versions

9 flagged

0.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.1.8

Indicators of compromise (SHA-256)

5ddee604833caafd5cbb937f26bb7f3254b700e7f03ca92cd370a3e1e2e853fc

afc5d216211e1025682d3292b3f7e94be1245a00904c4fb8008ae9cf0fefcff4

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for omniauth-pro-sante-connect (9 malicious versions).
If you installed it — respond
Remove omniauth-pro-sante-connect 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 omniauth-pro-sante-connect 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. omniauth-pro-sante-connect on RubyGems has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.1.7, and 1 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-04303RLUA-2025-06621

References

intel.aikido.dev

Credits

ReversingLabs · finder

Detect & block this

O3 blocks omniauth-pro-sante-connect-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