Which versions of @zarafront/lib-zds are malicious?

The following npm versions of @zarafront/lib-zds are flagged malicious: 99.50.55. Treat any of these as compromised.

How do I remediate @zarafront/lib-zds if I installed it?

Remove @zarafront/lib-zds 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 @zarafront/lib-zds — how do I know if it already compromised me?

If @zarafront/lib-zds 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 @zarafront/lib-zds part of a known attack campaign?

Yes — @zarafront/lib-zds is associated with the RLMA-2024-06090, RLUA-2026-10659 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 @zarafront/lib-zds 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 @zarafront/lib-zds (version 99.50.55). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @zarafront/lib-zds across your stack and pipelines.

Malicious package

@zarafront/lib-zdsnpm

@zarafront/lib-zds is a confirmed malicious npm package (MAL-2024-8838) that executes malicious code on install (malicious version 99.50.55). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zarafront/lib-zds (npm)

MAL-2024-8838

Immediate action

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

npm uninstall @zarafront/lib-zds

What this malware does

The OpenSSF Package Analysis project identified '@zarafront/lib-zds' @ 99.50.55 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

99.50.55

Indicators of compromise (SHA-256)

b7da81ddf52154f443baa27b56764a0be023447376bd6d8a3f587cc7db455f84

b666c1af13c0b686b376bca1567652a817ef4cd36a7ea17d2dc6838f5640a767

7cfdb80ff789b40130132d2799837687276f85b2241ec9229b766bcf640934bc

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

Campaign

RLMA-2024-06090RLUA-2026-10659

References

github.com

Credits

OpenSSF: Package Analysis · finder
ReversingLabs · finder

Detect & block this

O3 blocks @zarafront/lib-zds-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