Which versions of lowkeybored are malicious?

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

How do I remediate lowkeybored if I installed it?

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

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

Yes — lowkeybored is associated with the GHSA-5qp2-5jqf-v9h3, IN-MAL-2026-010451, RLMA-2026-05570, RLUA-2026-06314 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 lowkeybored 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 lowkeybored (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lowkeybored across your stack and pipelines.

Malicious package

lowkeyborednpm

lowkeybored is a confirmed malicious npm package (MAL-2026-10332) 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 lowkeybored (npm)

MAL-2026-10332

Immediate action

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

npm uninstall lowkeybored

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)

2f142ae0512feaeb848b0443a90bdb9372516559beaea415b4f7fdd9ef3f8f92

44a98aa46273662e37d16a9ce5fd2e003ae747c89301cbd03b1ba52bdbe81fca

cb803216815cc66c95d2cc45a869ab2fe8bad4904c65fad093f2e8d6d62a944f

c42748ad3d3e279b282f53d14e0da3bcc5066c722a8ebe9ddf0489c97fe53f7a

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 lowkeybored (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging lowkeybored across your stack and pipelines.
If you installed it — respond
Remove lowkeybored 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 lowkeybored 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 lowkeybored 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. lowkeybored 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-5qp2-5jqf-v9h3IN-MAL-2026-010451RLMA-2026-05570RLUA-2026-06314

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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