Which versions of alelo-services are malicious?

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

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

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

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

Yes — alelo-services is associated with the IN-MAL-2026-017730, IN-MAL-2026-017758, RLMA-2026-10688 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-services 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-services (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-services across your stack and pipelines.

Malicious package

alelo-servicesnpm

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

MAL-2026-14027

Immediate action

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

npm uninstall alelo-services

What this malware does

[email protected] runs both preinstall and postinstall lifecycle scripts that harvest installer data and POST it to the hardcoded bare-IP endpoint https://209.99.185.109 with TLS verification disabled (rejectUnauthorized:false). preinstall.js collects hostname, username, platform, cwd, and the entire process.env and sends the JSON to https://209.99.185.109/preinstall. index.js (also the package main, executed on postinstall) reads.env,.npmrc, package.json,../.env, and../../.env from the install directory, runs whoami/id, collects process.env, and POSTs the contents to https://209.99.185.109/postinstall. The.npmrc read captures npm auth tokens; the.env reads capture CI and cloud credentials from the installer and any parent project directories. Package metadata is generic ("internal utilities") and the 99.0.0 version is consistent with a dependency-confusion lure targeting a private scope name.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

00b5c557931bd8dd68451d2a88f2b69b54f7cba4e0dfcdc338abf5dd95472810

2b31cdc535ad02d3d78533315ef2037d4860699d9c7a161ed96a176082824f07

8da8d6619409dd8567afe5a61e5fbddffe6e7981a173f415d27e171ad05c7086

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-services (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-services across your stack and pipelines.
If you installed it — respond
alelo-services 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-services 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-services 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-services 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-017730IN-MAL-2026-017758RLMA-2026-10688

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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