Which versions of glob-helper are malicious?

The following npm versions of glob-helper are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0. Treat any of these as compromised.

How do I remediate glob-helper if I installed it?

glob-helper is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed glob-helper — how do I know if it already compromised me?

If glob-helper 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.

How do I find glob-helper across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for glob-helper (7 malicious versions).

Malicious package

glob-helpernpm

Advisory published May 14, 2026Updated May 15, 2026

glob-helper is a confirmed malicious npm package (MAL-2026-3764) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in glob-helper (npm)

MAL-2026-3764

Immediate action

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

npm uninstall glob-helper

What this malware does

[email protected] is a malicious typosquat with no legitimate functionality. Its index.js is a stub; package.json declares scripts.postinstall: node postinstall.js, which fires automatically on npm install. postinstall.js performs three concurrent credential-theft operations and POSTs the results as JSON over plain HTTP to a hardcoded bare-IP C2 at http://149.28.127.35:8888:

Reads ~/.npmrc (extracting authToken and npm* tokens), ~/.env (regex-matching NPM_TOKEN, NPM_AUTH_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN), and ~/.git-credentials.
Enumerates Chrome/Brave/Edge/Chromium/Vivaldi/Opera profile directories under ~/.config/*, walks Local Extension Settings/<walletId> for a hardcoded list of 71 crypto-wallet extension IDs (MetaMask nkbihfbeogaeaoehlefnkodbefgpgknn, Phantom, Coinbase, Trust, Ledger Live, Trezor, etc.), and greps log contents for vault, seed, mnemonic, privateKey, password, encrypted.
Walks ~/Documents, ~/Desktop, ~/Downloads for files whose names match seed|backup|wallet|phrase|metamask|phantom|vault|key|private, opens each, counts BIP39 wordlist matches, and includes file path + content preview in the exfil payload when 8+ BIP39 words are present.

The package.json keywords list lodash and the description is Glob Helper utility helpers, but index.js contains the author's own comment lodash-js — Just a dummy module. The real payload is in postinstall.js. Installing this package on any developer or CI machine leaks npm publish tokens, AWS keys, GitHub tokens, browser-stored wallet data, and any cryptocurrency seed backups present in the user's home directories.

Malicious versions

7 flagged

1.0.01.0.11.0.21.0.31.0.41.0.52.0.0

Indicators of compromise (SHA-256)

01930376eeb72450ef79dabbce9d88507e2ba93123f0356b95287fc674b72619

542fe088d2fee135e2cb5178360bdb390a963bd1be4dd816fb5d4dbd27b7ef87

74e3e047bbade54548ae02c0f98690df9a5c9392d94592600d71bc2e3de575e6

a5eda82b5edd6f7dc941f908a5d7d8b8dc76053f5bf141a97dbb9899c6de75cc

bf3e17ad2a01915e88251e0bb744239e1f1af4e8ed0f49ca2b0c433d9ef1814c

d2029b1bd45066f0e1f69d954404a7ad1480cceddc9850066c25519445fed1c4

091b8ee02b80a8a3fda11c15a6d0b8f657b639100244a4398d046ded5854eb64

2e4d100a1dc097212704ad4a8a071b2fa2b7aa6541181a5424cc013e2f7dfbf1

3ccf5efb2c9798c39005a553f2cc29d1541332cabee48e21916bed2d78ce2dd0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for glob-helper (7 malicious versions).
If you installed it — respond
glob-helper is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If glob-helper 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. glob-helper on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.0.4, 1.0.5, 2.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-002699IN-MAL-2026-002817IN-MAL-2026-002816IN-MAL-2026-002818IN-MAL-2026-002701IN-MAL-2026-002703IN-MAL-2026-002700IN-MAL-2026-002696IN-MAL-2026-002702

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks glob-helper-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database