Which versions of lowkirkuenly are malicious?

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

How do I remediate lowkirkuenly if I installed it?

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

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

Yes — lowkirkuenly is associated with the GHSA-78qq-4g2g-jp36, IN-MAL-2026-010420, RLMA-2026-05571, RLUA-2026-06315 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 lowkirkuenly 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 lowkirkuenly (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lowkirkuenly across your stack and pipelines.

Malicious package

lowkirkuenlynpm

lowkirkuenly is a confirmed malicious npm package (MAL-2026-10333) that executes malicious code on install (malicious versions 1.1.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lowkirkuenly (npm)

MAL-2026-10333

Immediate action

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

npm uninstall lowkirkuenly

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

2 flagged

1.1.22.0.0

Indicators of compromise (SHA-256)

1c86d89b5965c2190cca27e5c239d2999df8fb61b68f9670c779c032603fa892

1472fdafb97a66413947c670c93a1bce21ec72a95e47912e7093681e5d9cdb73

8918331e8fc062ccb533de6c090d64d13d63a6ea78c814ad1790129ecd0cd027

570d1040661005aab7eeceaf24b389b01789b756da41396ad3685404f1a24c26

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

Campaign

GHSA-78qq-4g2g-jp36IN-MAL-2026-010420RLMA-2026-05571RLUA-2026-06315

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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