Which versions of alelo-common are malicious?

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

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

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

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

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

Malicious package

alelo-commonnpm

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

MAL-2026-14023

Immediate action

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

npm uninstall alelo-common

What this malware does

The package auto-executes exfiltration code during npm install via preinstall and postinstall lifecycle scripts. preinstall.js collects the hostname, username, platform, cwd, and the full process.env, then POSTs the JSON payload to https://209.99.185.109/preinstall with TLS certificate validation disabled (rejectUnauthorized: false). index.js (postinstall) reads.env,.npmrc, package.json,../.env, and../../.env from the install directory, runs whoami and id, gathers process.env, and POSTs the aggregated payload to https://209.99.185.109/postinstall over the same TLS-disabled channel. The.npmrc read captures the installer's npm _authToken; the.env reads capture cloud, database, and API credentials. The destination is a bare-IP endpoint with no relationship to any legitimate publisher, and TLS verification is deliberately disabled. The package name resembles a private/internal scope, consistent with a dependency-confusion lure.

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

1f1e53c8bced61d4dfbd9121821219a5c35f2a7f273f06e9e2cfd628f509341f

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-common (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-common across your stack and pipelines.
If you installed it — respond
alelo-common 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-common 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-common 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-common 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-017755

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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