Which versions of halali-sample are malicious?

The following npm versions of halali-sample are flagged malicious: 999.9.14. Treat any of these as compromised.

How do I remediate halali-sample if I installed it?

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

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

Yes — halali-sample is associated with the RLMA-2026-10745 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 halali-sample across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for halali-sample (version 999.9.14).

Malicious package

halali-samplenpm

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in halali-sample (npm)

MAL-2026-16534

Immediate action

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

npm uninstall halali-sample

Malicious versions

1 flagged

999.9.14

Indicators of compromise (SHA-256)

8d2b0b2f512cec368fb40276de4a632deac03cd7ee28cc4db3977b9881d38054

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-10745

Credits

ReversingLabs · finder

Detect & block this

O3 blocks halali-sample-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