Which versions of eslint-plugin-dagster-rules are malicious?

The following npm versions of eslint-plugin-dagster-rules are flagged malicious: 1000.0.0, 1000.0.2, 1000.0.7. Treat any of these as compromised.

How do I remediate eslint-plugin-dagster-rules if I installed it?

Remove eslint-plugin-dagster-rules 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 eslint-plugin-dagster-rules — how do I know if it already compromised me?

If eslint-plugin-dagster-rules 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 eslint-plugin-dagster-rules part of a known attack campaign?

Yes — eslint-plugin-dagster-rules is associated with the RLMA-2026-05074, RLUA-2026-06215 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 eslint-plugin-dagster-rules across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for eslint-plugin-dagster-rules (3 malicious versions).

Malicious package

eslint-plugin-dagster-rulesnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

eslint-plugin-dagster-rules is a confirmed malicious npm package (MAL-2026-7281) that executes malicious code on install (malicious versions 1000.0.0, 1000.0.2, 1000.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in eslint-plugin-dagster-rules (npm)

MAL-2026-7281

Immediate action

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

npm uninstall eslint-plugin-dagster-rules

Malicious versions

3 flagged

1000.0.01000.0.21000.0.7

Indicators of compromise (SHA-256)

d609cfb7a513d4b15f7e6df298f463bf6ddedbd08c79872651685ba06b6f045c

33e51a06dd63d431b9b291781dad93b5699f934d14c957ec5fa2400fec6bda78

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for eslint-plugin-dagster-rules (3 malicious versions).
If you installed it — respond
Remove eslint-plugin-dagster-rules 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 eslint-plugin-dagster-rules 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. eslint-plugin-dagster-rules on npm has been identified as a malicious package (versions 1000.0.0, 1000.0.2, 1000.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05074RLUA-2026-06215

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks eslint-plugin-dagster-rules-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