Which versions of env-fast are malicious?

The following npm versions of env-fast are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate env-fast if I installed it?

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

If env-fast was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is env-fast part of a known attack campaign?

Yes — env-fast is associated with the IN-MAL-2026-010207 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 env-fast across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for env-fast (version 1.0.0).

Malicious package

env-fastnpm

Advisory published Jul 13, 2026Updated Jul 13, 2026

env-fast is a confirmed malicious npm package (MAL-2026-10434) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in env-fast (npm)

MAL-2026-10434

Immediate action

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

npm uninstall env-fast

What this malware does

[email protected] presents as a zero-dependency env loader but on require schedules a 72-hour-delayed activation that POSTs a host fingerprint (hostname, platform, release, arch, CPU/memory, homedir, network interface names, uptime, node version) to hardcoded bare-IP endpoint http://2.27.62.51:8080/api/health over plain HTTP, followed by a 6-hour heartbeat. The same payload probes installer secret locations — reports presence of ~/.npmrc, enumerates ~/.ssh for id_rsa/id_ed25519/id_ecdsa, and counts process.env keys matching /key|secret|token|password|auth|private|wallet|seed|mnemonic/i — and ships those results to the same remote endpoint. The 72-hour dormancy is a behavioral evasion pattern that avoids short-lived CI and sandbox environments while ensuring long-lived production hosts trigger the beacon.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

9955128054ee66cd4675be3884e92f9e541ad7e9673496ece60e932c0b83ca5f

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for env-fast (version 1.0.0).
If you installed it — respond
env-fast 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 env-fast was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. env-fast on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010207

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks env-fast-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