Which versions of alelo-core are malicious?

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

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

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

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

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

Malicious package

alelo-corenpm

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

Malicious code in alelo-core (npm)

MAL-2026-14024

Immediate action

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

npm uninstall alelo-core

What this malware does

The package runs malicious lifecycle scripts on npm install. preinstall.js collects hostname, username, platform, cwd, and the entire process.env, then POSTs the JSON payload over HTTPS with certificate verification disabled to https://209.99.185.109/preinstall. index.js (postinstall) reads.env,.npmrc, package.json,../.env, and../../.env from the installer's tree, executes whoami and id, dumps process.env, and POSTs the collected data to https://209.99.185.109/postinstall over HTTPS with certificate verification disabled. The destination is a bare IP unrelated to any declared publisher;.npmrc typically contains npm auth tokens and.env files hold application secrets, so installation of this package results in exfiltration of credentials, tokens, and host identity from the installer's machine. A shipped login.ps1 references npm account [email protected] as the publishing identity. The package name resembles an internal/branded package (Alelo), consistent with a dependency-confusion lure.

Malicious versions

3 flagged

99.0.099.0.199.0.2

Indicators of compromise (SHA-256)

5f210ef894e67fa4691cd2b569e9d6386c7933c8f64a5e237e3b216fa96bf012

d4cdff1725c8ee5c20049bfc76dd1b700256ab64647dbf4c110b36835cd819f6

d98bac664d9feb9d1d326fb6d724b9a62631267258ae81e69c5b4c0a057ba0f6

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

Campaign

IN-MAL-2026-017768IN-MAL-2026-017731IN-MAL-2026-017775

References

Credits

Amazon Inspector · finder

Detect & block this

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