Which versions of alelo-client are malicious?

The following npm versions of alelo-client are flagged malicious: 99.0.0, 99.0.2. Treat any of these as compromised.

How do I remediate alelo-client if I installed it?

alelo-client 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 alelo-client — how do I know if it already compromised me?

If alelo-client 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 alelo-client part of a known attack campaign?

Yes — alelo-client is associated with the IN-MAL-2026-017773, IN-MAL-2026-017728 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 alelo-client 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 alelo-client (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging alelo-client across your stack and pipelines.

Malicious package

alelo-clientnpm

alelo-client is a confirmed malicious npm package (MAL-2026-14022) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alelo-client (npm)

MAL-2026-14022

Immediate action

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

npm uninstall alelo-client

What this malware does

[email protected] is a dependency-confusion / impersonation package targeting an internal 'Alelo' namespace (version 99.0.0, generic 'internal utilities' description). On npm install, preinstall.js collects hostname, username, platform, cwd, and the full process.env and POSTs the JSON payload over HTTPS to the bare-IP endpoint https://209.99.185.109/preinstall with TLS verification disabled (rejectUnauthorized:false). A postinstall path additionally reads.env,.npmrc, package.json, and parent-directory.env files via fs.readFileSync, executes whoami/id via child_process, and POSTs the collected contents to https://209.99.185.109/postinstall with certificate verification disabled. The tarball also ships a login.ps1 referencing an external npm account ([email protected]). The.npmrc read yields the installer's npm auth token and the.env reads yield application secrets; both leave the installer's machine to an attacker-controlled bare IP at install time.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

6898fc8ceef98678ef5e208de13006abf0684d219babdee50f6f90b732092f8b

70e03bbda3ad266c44d9adc5998938e5abc800274ed0604f4688fa0d3139402f

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 alelo-client (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging alelo-client across your stack and pipelines.
If you installed it — respond
alelo-client 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 alelo-client 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 alelo-client 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. alelo-client on npm has been identified as a malicious package (versions 99.0.0, 99.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-017773IN-MAL-2026-017728

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks alelo-client-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