Which versions of glia-functions-tools are malicious?

The following npm versions of glia-functions-tools are flagged malicious: 0.2.1, 1.2.1. Treat any of these as compromised.

How do I remediate glia-functions-tools if I installed it?

glia-functions-tools 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 glia-functions-tools — how do I know if it already compromised me?

If glia-functions-tools 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 glia-functions-tools part of a known attack campaign?

Yes — glia-functions-tools is associated with the IN-MAL-2026-014962, GHSA-62wp-x489-6g6h, IN-MAL-2026-019814 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 glia-functions-tools 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 glia-functions-tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glia-functions-tools across your stack and pipelines.

Malicious package

glia-functions-toolsnpm

glia-functions-tools is a confirmed malicious npm package (MAL-2026-12790) that steals credentials and exfiltrates sensitive data (malicious versions 0.2.1, 1.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in glia-functions-tools (npm)

MAL-2026-12790

Immediate action

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

npm uninstall glia-functions-tools

What this malware does

package.json's preinstall hook runs index.js, which collects hostname, username, home directory, DNS servers, and current working directory, reads /etc/passwd and /etc/hosts, and HTTPS-POSTs the JSON payload to a hardcoded Burp Collaborator (oastify.com) subdomain. The exfiltration fires automatically on npm install without any user interaction, and targets installer-side system identity and account data.

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

2 flagged

0.2.11.2.1

Indicators of compromise (SHA-256)

e24f6c700225d22dcccdf1af7bb58c7628366ccc59b864431af5123909b42626

e043a7baa55d15e554e0043a67f74acddbcf0e5ca437783bb551b6b0a4458b65

a87fea856cfb4016a322ca6f43c8819d296b3fbf50a06f4afe86b495ba5e2997

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for glia-functions-tools (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging glia-functions-tools across your stack and pipelines.
If you installed it — respond
glia-functions-tools 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 glia-functions-tools 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 glia-functions-tools 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. glia-functions-tools on npm has been identified as a malicious package (versions 0.2.1, 1.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-014962GHSA-62wp-x489-6g6hIN-MAL-2026-019814

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks glia-functions-tools-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