Which versions of alelo-sdk are malicious?

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

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

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

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

Yes — alelo-sdk is associated with the IN-MAL-2026-017766, IN-MAL-2026-017767, RLMA-2026-10687 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-sdk 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-sdk (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-sdk across your stack and pipelines.

Malicious package

alelo-sdknpm

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

MAL-2026-14026

Immediate action

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

npm uninstall alelo-sdk

What this malware does

[email protected] ships lifecycle scripts that harvest installer data and POST it to a hardcoded bare-IP endpoint (209.99.185.109) with TLS certificate verification disabled. preinstall.js collects hostname, username, platform, cwd, and the full process.env and sends the JSON to https://209.99.185.109/preinstall. The postinstall path (index.js) additionally reads.env,.npmrc, and parent-directory.env files, executes whoami/id, and POSTs the collected content to https://209.99.185.109/postinstall..npmrc typically contains npm publish tokens and.env files typically contain cloud and API credentials, so any environment where this package is installed (developer workstation or CI) has its secrets extracted. Package metadata (name 'alelo-sdk', version 99.0.0, description 'internal utilities', author 'Alelo Dev Team') is the canonical dependency-confusion shape targeting a private 'alelo' internal scope with an inflated version number.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

4e7ed1d4017e58a9911a0cfee5d1cf8122a2ac28779a36fdf3ef74484f048748

af6934bd17136e982088e7bb52509b78f925d386c8f541d4f3cf3b2e1a8f6d43

34e73061b448766a54311299a23bea18ad8450103890848354d2919ab375b2db

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-sdk (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-sdk across your stack and pipelines.
If you installed it — respond
alelo-sdk 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-sdk 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-sdk 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-sdk 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-017766IN-MAL-2026-017767RLMA-2026-10687

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

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