Which versions of @irys-solutions/odesa-main are malicious?

The following npm versions of @irys-solutions/odesa-main are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @irys-solutions/odesa-main if I installed it?

@irys-solutions/odesa-main is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @irys-solutions/odesa-main — how do I know if it already compromised me?

If @irys-solutions/odesa-main 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 @irys-solutions/odesa-main part of a known attack campaign?

Yes — @irys-solutions/odesa-main is associated with the RLMA-2026-05434, IN-MAL-2026-013255, RLUA-2026-05878 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 @irys-solutions/odesa-main across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @irys-solutions/odesa-main (version 1.0.0).

Malicious package

@irys-solutions/odesa-mainnpm

Advisory published Jul 20, 2026Updated Sep 1, 2026

@irys-solutions/odesa-main is a confirmed malicious npm package (MAL-2026-10881) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @irys-solutions/odesa-main (npm)

MAL-2026-10881

Immediate action

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

npm uninstall @irys-solutions/odesa-main

What this malware does

No malicious behavior was identified in this package version. No lifecycle scripts performing remote fetches, no credential reads, no exfiltration endpoints, and no suspicious code patterns were observed. With only two files in the package and no concerning content, there is no evidence of installer-side harm.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

3f20fc0b546aeb9bdc71496f30839ce40239b21a9e133237b35e3f5f28078cba

525ae6b33885c1153dac485b830c8977b433ba4cdd2cc9556415b146ed801569

c355ce2b7e587ca55ec965d0a97bbee29cb7f51504d715455ee6b4e48dfd99be

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @irys-solutions/odesa-main (version 1.0.0).
If you installed it — respond
@irys-solutions/odesa-main is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @irys-solutions/odesa-main 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. @irys-solutions/odesa-main on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05434IN-MAL-2026-013255RLUA-2026-05878

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @irys-solutions/odesa-main-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database