Which versions of @global-theme/context are malicious?

The following npm versions of @global-theme/context are flagged malicious: 99.9.1. Treat any of these as compromised.

How do I remediate @global-theme/context if I installed it?

Remove @global-theme/context 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 @global-theme/context — how do I know if it already compromised me?

If @global-theme/context 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 @global-theme/context part of a known attack campaign?

Yes — @global-theme/context is associated with the GHSA-whq3-7x3r-pv39, RLMA-2026-05867, RLUA-2026-10634 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 @global-theme/context across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @global-theme/context (version 99.9.1).

Malicious package

@global-theme/contextnpm

Advisory published Jul 31, 2026Updated Sep 24, 2026

@global-theme/context is a confirmed malicious npm package (MAL-2026-11439) that executes malicious code on install (malicious version 99.9.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @global-theme/context (npm)

MAL-2026-11439

Immediate action

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

npm uninstall @global-theme/context

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

99.9.1

Indicators of compromise (SHA-256)

b48962d911b70fd09f4c001b44b879452dda607f877256d2f85d64538912ab7f

716c103d81c20fb66129d20b84f181656632dbf957755a00e7871e1fd40a1662

76c927e989cdb9daa9e96bc3f3ba4e1c652437c937d8a46a0d69299eeb8432e8

Detection & response playbook

Malicious package

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

Campaign

GHSA-whq3-7x3r-pv39RLMA-2026-05867RLUA-2026-10634

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @global-theme/context-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