Which versions of resource-library-engine are malicious?

The following npm versions of resource-library-engine are flagged malicious: 99.99.99. Treat any of these as compromised.

How do I remediate resource-library-engine if I installed it?

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

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

Yes — resource-library-engine is associated with the RLMA-2026-05280, RLUA-2026-06445 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 resource-library-engine across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for resource-library-engine (version 99.99.99).

Malicious package

resource-library-enginenpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

resource-library-engine is a confirmed malicious npm package (MAL-2026-7387) 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 resource-library-engine (npm)

MAL-2026-7387

Immediate action

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

npm uninstall resource-library-engine

Malicious versions

1 flagged

99.99.99

Indicators of compromise (SHA-256)

60eb7dcbabaf93190a37578c08f63c404a345cd2f5d5c1751b0f29b860b98e2e

0efa327f3a531daff2ba6ae9b7edc1284113ee6a9668352fade78e5a01e8d23a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for resource-library-engine (version 99.99.99).
If you installed it — respond
Remove resource-library-engine 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 resource-library-engine 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. resource-library-engine 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-05280RLUA-2026-06445

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks resource-library-engine-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