Which versions of alelo-api are malicious?

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

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

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

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

Yes — alelo-api is associated with the IN-MAL-2026-017769, IN-MAL-2026-017770 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-api 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-api (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-api across your stack and pipelines.

Malicious package

alelo-apinpm

alelo-api is a confirmed malicious npm package (MAL-2026-14020) 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-api (npm)

MAL-2026-14020

Immediate action

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

npm uninstall alelo-api

What this malware does

The package fires attacker-controlled code on npm install via both preinstall.js and index.js (postinstall). preinstall.js collects hostname, username, platform, cwd, and the full process.env, JSON-encodes it, and POSTs it over HTTPS with TLS verification disabled to the hardcoded bare-IP endpoint https://209.99.185.109/preinstall. The postinstall path reads installer-owned secret files from the current working directory and its parents (.env, ../.env, ../../.env, .npmrc, package.json), captures process.env, executes whoami and id, and POSTs the aggregate to https://209.99.185.109/postinstall (also with TLS verification disabled). The tarball additionally ships a login.ps1 note referencing the publisher account [email protected] and a local publish workflow under C:\Users\hp\Documents\alelo\npm-publish; combined with the name alelo-api and version 99.0.0, this indicates a typosquat / dependency-confusion attack aimed at the Alelo organization. Any installer that runs npm install alelo-api leaks environment variables, npm tokens, and any .env secrets in the working tree to the hardcoded IP.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

0e520850363c3164a09e0772022283849a0abd1b6f60e9168f4a5fd3ff338886

a2f51421bbedaeb1c9c0bd34829ebad9224a41068662bc855d20c06f7d2cc3b6

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-api (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-api across your stack and pipelines.
If you installed it — respond
alelo-api 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-api 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-api 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-api 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-017769IN-MAL-2026-017770

References

Credits

Amazon Inspector · finder

Detect & block this

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