Which versions of mvn-runtime are malicious?

The following npm versions of mvn-runtime are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate mvn-runtime if I installed it?

Remove mvn-runtime 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 mvn-runtime — how do I know if it already compromised me?

If mvn-runtime 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 mvn-runtime part of a known attack campaign?

Yes — mvn-runtime is associated with the GHSA-5937-7cj9-h84g, RLMA-2026-01436, RLUA-2026-01789 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 mvn-runtime 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 mvn-runtime (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mvn-runtime across your stack and pipelines.

Malicious package

mvn-runtimenpm

Malicious code in mvn-runtime (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1202

Immediate action

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

npm uninstall mvn-runtime

What this malware does

The package mvn-runtime 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

1 flagged

1.0.1

Indicators of compromise (SHA-256)

3af620cf3afd7a0d522823f8835bdf289b697f5be39cf61e22e7f1f0da6ec7aa

d7439c73d7a34dad9485537cc4adefa71514a16e38e08a171c099933110bfa5c

a619ffab2d89d6d8ca4887804a98c52a28d0984ee004e1b79272b6a5884d9e5e

980969c3784d895ce05601276a073718147ecb9e2b6b81f66b92c6d14e43867f

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 mvn-runtime (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mvn-runtime across your stack and pipelines.
If you installed it — respond
Remove mvn-runtime 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 mvn-runtime 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 mvn-runtime 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. mvn-runtime on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5937-7cj9-h84gRLMA-2026-01436RLUA-2026-01789

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks mvn-runtime-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