Which versions of @driivz/component-library are malicious?

The following npm versions of @driivz/component-library are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate @driivz/component-library if I installed it?

Remove @driivz/component-library 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 @driivz/component-library — how do I know if it already compromised me?

If @driivz/component-library 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 @driivz/component-library part of a known attack campaign?

Yes — @driivz/component-library is associated with the RLMA-2026-04714, RLUA-2026-05849 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 @driivz/component-library across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @driivz/component-library (version 99.99.99).

Malicious package

@driivz/component-librarynpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@driivz/component-library is a confirmed malicious npm package (MAL-2026-7067) that executes malicious code on install (malicious version 99.99.99). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @driivz/component-library (npm)

MAL-2026-7067

Immediate action

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

npm uninstall @driivz/component-library

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

db454bc47987135b1921c0b64b78844470d6e89deaa10e55cb679ec14c2fb1e9

e58be95675563b281acc0d4abeb44eee88718b37fec033ab98debfeeefdc89b7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04714RLUA-2026-05849

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @driivz/component-library-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