Which versions of alelo-utils are malicious?

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

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

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

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

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

Malicious package

alelo-utilsnpm

alelo-utils is a confirmed malicious npm package (MAL-2026-14028) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in alelo-utils (npm)

MAL-2026-14028

Immediate action

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

npm uninstall alelo-utils

What this malware does

On npm install, preinstall.js collects hostname, username, platform, cwd and the full process.env and POSTs the JSON body to https://209.99.185.109/preinstall with TLS verification disabled (rejectUnauthorized:false). A companion postinstall/index.js path reads.env,.npmrc, package.json, and parent-directory.env files (../.env,../../.env), runs whoami/id via child_process, and POSTs the collected contents to https://209.99.185.109/postinstall over the same TLS-disabled channel. The destination is a bare IPv4 endpoint unrelated to any documented publisher. Package metadata shows a dependency-confusion shape: name alelo-utils published at version 99.0.0, and a bundled login.ps1 references an npm publish workflow under the personal account [email protected], which does not match the claimed 'Alelo Dev Team' author..npmrc typically contains npm _authToken values and.env commonly holds cloud/API credentials, so this install-time flow directly exfiltrates installer credentials.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

5b1fd03e0ca4d5452b6a5d6aa2880a9c711021e287eaae056e68f70f6aedc926

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

Campaign

IN-MAL-2026-017760

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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