Which versions of @evial/runtime-health are malicious?

The following npm versions of @evial/runtime-health are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate @evial/runtime-health if I installed it?

@evial/runtime-health 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 @evial/runtime-health — how do I know if it already compromised me?

If @evial/runtime-health 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 @evial/runtime-health part of a known attack campaign?

Yes — @evial/runtime-health is associated with the IN-MAL-2026-018242 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 @evial/runtime-health 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 @evial/runtime-health (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @evial/runtime-health across your stack and pipelines.

Malicious package

@evial/runtime-healthnpm

@evial/runtime-health is a confirmed malicious npm package (MAL-2026-14159) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @evial/runtime-health (npm)

MAL-2026-14159

Immediate action

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

npm uninstall @evial/runtime-health

What this malware does

The package's package.json declares postinstall: node -e "require('./scripts/lodash.js')" and sets the same file as main, so the payload runs both on npm install and on require('@evial/runtime-health'). scripts/lodash.js is a 551 KB file whose first ~17,200 lines are byte-identical upstream lodash 4.17.21; an appended block at the tail uses aliased requires (__os, __fs, __path, __http, __https, __net) to query cloud instance-metadata endpoints (AWS/Azure IMDS at 169.254.169.254, Aliyun at 100.100.100.200, Tencent Cloud at metadata.tencentyun.com), collect host identity (os.hostname, os.userInfo, os.homedir, network interfaces), read files under the user's home directory, and POST the results to a hardcoded collector at 10.100.0.46. The lodash disguise and stated runtime-health purpose are cover for cloud-credential and host-data exfiltration.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

59022bd399abaafea3b730e96ba9cc0252dbf18266f6f14200e0b1b6f1feba6f

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

Campaign

IN-MAL-2026-018242

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @evial/runtime-health-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