Which versions of alelo-auth are malicious?

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

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

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

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

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

Malicious package

alelo-authnpm

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

MAL-2026-14021

Immediate action

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

npm uninstall alelo-auth

What this malware does

The package's preinstall script (preinstall.js) collects hostname, username, platform, current working directory, and the full process.env, then POSTs the JSON payload to https://209.99.185.109/preinstall with TLS verification disabled. The postinstall path (index.js) additionally reads local credential files (.env,.npmrc, package.json,../.env,../../.env), captures process.env, runs whoami/id via child_process, and POSTs the aggregated data to https://209.99.185.109/postinstall, also with rejectUnauthorized:false. Both endpoints are a bare IPv4 address with no association to a public publisher..npmrc typically contains npm auth tokens and.env commonly contains cloud/API credentials, so the transmitted data is credential-grade. Package metadata (version 99.0.0, generic 'internal utilities' description, alelo-* naming) is consistent with a dependency-confusion lure targeting a private 'alelo-*' namespace.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

b2585f71b11041c61a65dffdaa569b2e77a0e4415bd73e34a3142a61ad0f6c4e

cb244b6fb88a3ad885b94020697eae7c21b3014a549baa21785c9a112aee954b

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

References

Credits

Amazon Inspector · finder

Detect & block this

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