Which versions of ls-env-config are malicious?

The following npm versions of ls-env-config are flagged malicious: 1.0.5. Treat any of these as compromised.

How do I remediate ls-env-config if I installed it?

ls-env-config establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed ls-env-config — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for ls-env-config (version 1.0.5).

Malicious package

ls-env-confignpm

Advisory published Jul 15, 2026Updated Jul 15, 2026

ls-env-config is a confirmed malicious npm package (MAL-2026-10678) that opens a backdoor for remote access (malicious version 1.0.5). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ls-env-config (npm)

MAL-2026-10678

Immediate action

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

npm uninstall ls-env-config

What this malware does

Package declares a preinstall script (node./index.js) that fires automatically on npm install. The executed index.js issues an HTTP GET to a Burp-Collaborator-style subdomain at 85324cf9ac5145428803ea[...].collaborator.zivyelab.com/hello01?test=01. This confirms code execution on the installer's machine and a DNS/HTTP callback to a non-first-party host on every install, leaking host and network reachability information. The pattern is consistent with a dependency-confusion probe; regardless of stated intent, it executes on any installer and beacons to a third-party collaborator endpoint.

Malicious versions

1 flagged

1.0.5

Indicators of compromise (SHA-256)

db44619df34ccbffa5747f17c8135602583a781ec01f8d3c03e0f828157e944c

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for ls-env-config (version 1.0.5).
If you installed it — respond
ls-env-config establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If ls-env-config 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. ls-env-config on npm has been identified as a malicious package (version 1.0.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010677

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks ls-env-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database