Which versions of meualelo are malicious?

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

How do I remediate meualelo if I installed it?

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

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

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

Malicious package

meualelonpm

meualelo is a confirmed malicious npm package (MAL-2026-14033) 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 meualelo (npm)

MAL-2026-14033

Immediate action

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

npm uninstall meualelo

What this malware does

The package's preinstall.js collects hostname, username, platform, cwd, and the full process.env, then POSTs the JSON payload over HTTPS (with TLS verification disabled via rejectUnauthorized:false) to the hardcoded bare-IP endpoint https://209.99.185.109/preinstall. index.js (postinstall path) additionally reads.env,.npmrc, package.json, and parent-directory.env files, runs whoami/id, and ships the collected contents plus full process.env to https://209.99.185.109/postinstall..npmrc typically contains the installer's npm _authToken and.env commonly contains cloud, database, and CI credentials. The package presents itself with author 'Alelo Dev Team' at version 99.0.0 while a bundled login.ps1 references a personal proton.me account for npm publishing, consistent with brand impersonation of Alelo.

Malicious versions

2 flagged

99.0.099.0.2

Indicators of compromise (SHA-256)

6fdf84c3f49f6d13b7ccbed745056f8bf03c4c7a2b814152962361ac07bd4191

d438fad1187890e7e3fe3d79a212f846b80dcca34f3019aa68c80b2419205eda

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 meualelo (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging meualelo across your stack and pipelines.
If you installed it — respond
meualelo 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 meualelo 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 meualelo 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. meualelo 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-017754RLMA-2026-10761

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks meualelo-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