Which versions of kirkland are malicious?

The following npm versions of kirkland are flagged malicious: 1.1.2. Treat any of these as compromised.

How do I remediate kirkland if I installed it?

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

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

Yes — kirkland is associated with the GHSA-7m92-3w8w-hxrp, RLMA-2026-05565, RLUA-2026-06295 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 kirkland across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for kirkland (version 1.1.2).

Malicious package

kirklandnpm

Advisory published Jul 13, 2026Updated Sep 1, 2026

kirkland is a confirmed malicious npm package (MAL-2026-10331) that executes malicious code on install (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in kirkland (npm)

MAL-2026-10331

Immediate action

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

npm uninstall kirkland

What this malware does

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.1.2

Indicators of compromise (SHA-256)

4fbd3da78615dc607bb287e809874ccce081e816a5eeb1120421118da70bcba5

d63227409d50f6692f439affe3fa27016710894dd8c9882559b0424f26a2e5e8

2262ab0c908e59abf21c020e17ee128b0456636c50be5704d08508a7890092a3

Detection & response playbook

Malicious package

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

Campaign

GHSA-7m92-3w8w-hxrpRLMA-2026-05565RLUA-2026-06295

References

Credits

ReversingLabs · finder

Detect & block this

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