Which versions of @patternfly-4/quickstarts are malicious?

The following npm versions of @patternfly-4/quickstarts are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate @patternfly-4/quickstarts if I installed it?

Remove @patternfly-4/quickstarts 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 @patternfly-4/quickstarts — how do I know if it already compromised me?

If @patternfly-4/quickstarts 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 @patternfly-4/quickstarts part of a known attack campaign?

Yes — @patternfly-4/quickstarts is associated with the GHSA-9xpj-3r3g-x2gh, RLMA-2026-05894, RLUA-2026-10645 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 @patternfly-4/quickstarts across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @patternfly-4/quickstarts (version 9.9.9).

Malicious package

@patternfly-4/quickstartsnpm

Advisory published Jul 30, 2026Updated Sep 24, 2026

@patternfly-4/quickstarts is a confirmed malicious npm package (MAL-2026-11219) that executes malicious code on install (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @patternfly-4/quickstarts (npm)

MAL-2026-11219

Immediate action

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

npm uninstall @patternfly-4/quickstarts

What this malware does

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

1 flagged

9.9.9

Indicators of compromise (SHA-256)

ad5c84bc12cb0c8215b572e242d8268710430f7bb4c16d7ce4ac25a072cd39e9

5cc2209a5b01ae802a0fb5ee077e81b3e81f73c178459c5233ef28c2a707b8c5

ce8661421ac1d38bf8ffaa0f8b432b2ece29ec4f60124ff39879a317ed20902f

Detection & response playbook

Malicious package

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

Campaign

GHSA-9xpj-3r3g-x2ghRLMA-2026-05894RLUA-2026-10645

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @patternfly-4/quickstarts-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