Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mjs-eslint-servicenpm

mjs-eslint-service is a confirmed malicious npm package (MAL-2026-6333) that executes malicious code on install (malicious version 7.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in mjs-eslint-service (npm)

MAL-2026-6333
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall mjs-eslint-service

What this malware does

The package was found to contain malicious code or consuming dependency that contains 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

1 flagged
7.0.5

Indicators of compromise (SHA-256)

976e104551fb8019a7f905830a468229da9572b6ca5dc3b9e2b00e2140fe2c05
f7e95cb81c6a1238d751c013def46001948b388083e0d91f7baa5077091ae006

Detection & response playbook

Malicious package
  1. Find it

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

  2. If you installed it — respond

    Remove mjs-eslint-service 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.

  3. Did it already run?

    If mjs-eslint-service 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.

  4. How O3 protects you

    O3 blocks mjs-eslint-service 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. mjs-eslint-service on npm has been identified as a malicious package (version 7.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jwg8-mccp-c3vgIN-MAL-2026-008513

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks mjs-eslint-service-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.

Explore

mjs-eslint-service (npm) malicious package — MAL-2026-6333 | O3 Security