Which versions of gleb-js are malicious?

The following npm versions of gleb-js are flagged malicious: 1.2.0. Treat any of these as compromised.

How do I remediate gleb-js if I installed it?

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

If gleb-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is gleb-js part of a known attack campaign?

Yes — gleb-js is associated with the GHSA-gxf7-922p-wp6q, RLMA-2026-05103 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 gleb-js across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gleb-js (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gleb-js across your stack and pipelines.

Malicious package

gleb-jsnpm

gleb-js is a confirmed malicious npm package (MAL-2026-2976) that executes malicious code on install (malicious version 1.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gleb-js (npm)

MAL-2026-2976

Immediate action

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

npm uninstall gleb-js

What this malware does

The package gleb-js was found to contain malicious code.

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

1.2.0

Indicators of compromise (SHA-256)

24151762712a7288d42bf902b1d0d205f13c6f76668490e7043fe846a8fd241f

1195db21d930574e3f893e03ace1f465579fc9a50f319979b05f57a0a6d8e252

f9fe9aa37ab32cc8ad733a613fa10cf80f579468f31e02752ddf76d8c2b692f4

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gleb-js (version 1.2.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gleb-js across your stack and pipelines.
If you installed it — respond
Remove gleb-js 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 gleb-js was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks gleb-js before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. gleb-js on npm has been identified as a malicious package (version 1.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gxf7-922p-wp6qRLMA-2026-05103

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks gleb-js-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