Which versions of lunkr are malicious?

The following npm versions of lunkr are flagged malicious: 1.1.1, 1.1.4, 8.7.6. Treat any of these as compromised.

How do I remediate lunkr if I installed it?

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

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

Yes — lunkr is associated with the RLMA-2026-05148, RLUA-2026-06317 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 lunkr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lunkr (3 malicious versions).

Malicious package

lunkrnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

lunkr is a confirmed malicious npm package (MAL-2026-7316) that executes malicious code on install (malicious versions 1.1.1, 1.1.4, 8.7.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lunkr (npm)

MAL-2026-7316

Immediate action

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

npm uninstall lunkr

Malicious versions

3 flagged

1.1.11.1.48.7.6

Indicators of compromise (SHA-256)

c0cc95292ec3541c9cf8f9503cab5ad12e233f24e2cb2eaf55be1190ca2269a5

d21c13892b96b205ed6a1001c8b0d0ef9a6e3012eac217bdca7823c2457afe99

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-05148RLUA-2026-06317

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks lunkr-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