Which versions of @gs-select/client-sbl-application are malicious?

The following npm versions of @gs-select/client-sbl-application are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @gs-select/client-sbl-application if I installed it?

Remove @gs-select/client-sbl-application 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 @gs-select/client-sbl-application — how do I know if it already compromised me?

If @gs-select/client-sbl-application 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 @gs-select/client-sbl-application part of a known attack campaign?

Yes — @gs-select/client-sbl-application is associated with the RLMA-2026-04730, RLUA-2026-05871 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 @gs-select/client-sbl-application across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @gs-select/client-sbl-application (version 99.0.0).

Malicious package

@gs-select/client-sbl-applicationnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

@gs-select/client-sbl-application is a confirmed malicious npm package (MAL-2026-7072) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @gs-select/client-sbl-application (npm)

MAL-2026-7072

Immediate action

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

npm uninstall @gs-select/client-sbl-application

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

fa809a5d04c0e267b137c20076c9a1e4a18fa276b802e54a82e09dda30c1946a

8204ab5d358d12b2110372857bc6767966e66f7f4dfce8bd3cbf9f07fbb24d22

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04730RLUA-2026-05871

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks @gs-select/client-sbl-application-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