Which versions of eslint-config-minecraft-scripting are malicious?

The following npm versions of eslint-config-minecraft-scripting are flagged malicious: 19.9.9, 99.0.0, 99.9.9. Treat any of these as compromised.

How do I remediate eslint-config-minecraft-scripting if I installed it?

Remove eslint-config-minecraft-scripting 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-config-minecraft-scripting — how do I know if it already compromised me?

If eslint-config-minecraft-scripting 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.

Is eslint-config-minecraft-scripting part of a known attack campaign?

Yes — eslint-config-minecraft-scripting is associated with the GHSA-rh9x-2vc7-83hh, RLMA-2026-01295 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-config-minecraft-scripting across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-config-minecraft-scripting (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-minecraft-scripting across your stack and pipelines.

Malicious package

eslint-config-minecraft-scriptingnpm

Malicious code in eslint-config-minecraft-scripting (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-634

Immediate action

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

npm uninstall eslint-config-minecraft-scripting

What this malware does

The package eslint-config-minecraft-scripting 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

3 flagged

19.9.999.0.099.9.9

Indicators of compromise (SHA-256)

965724c03399dbf45fac622dbfa8cb38e94e6cf7e3c137390da6e2818b9f073b

ebd11584eca4f0fcd95c2f2f7b250703fc0b68ec7d45c50cac4a5f22f846d20a

e0513cf60f6218a13ee19e9dbb9775f227a59ab56468efcdacba31d696b99656

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for eslint-config-minecraft-scripting (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging eslint-config-minecraft-scripting across your stack and pipelines.
If you installed it — respond
Remove eslint-config-minecraft-scripting 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-config-minecraft-scripting 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.
How O3 protects you
O3 blocks eslint-config-minecraft-scripting 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. eslint-config-minecraft-scripting on npm has been identified as a malicious package (versions 19.9.9, 99.0.0, 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rh9x-2vc7-83hhRLMA-2026-01295

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks eslint-config-minecraft-scripting-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