Which versions of environment-gate are malicious?

The following npm versions of environment-gate are flagged malicious: 7.3.5, 7.3.6. Treat any of these as compromised.

How do I remediate environment-gate if I installed it?

Remove environment-gate from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed environment-gate — how do I know if it already compromised me?

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

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

Malicious package

environment-gatenpm

environment-gate is a confirmed malicious npm package (MAL-2026-5743) that executes malicious code on install (malicious versions 7.3.5, 7.3.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in environment-gate (npm)

MAL-2026-5743

Immediate action

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

npm uninstall environment-gate

What this malware does

index.js contains a commented-out line that, if uncommented, would base64-decode the URL https://www.jsonkeeper.com/b/VKUNI, fetch its contents via axios, and eval the response. As shipped the code is inside a // comment and does not execute on require() or install — the only live code is a misspelled conosle.log and the package's gate export is a no-op. No lifecycle hooks are declared in package.json. There is no current installer-side harm in this version, but the presence of a fully-formed remote-fetch-and-eval template targeting an anonymous, mutable paste host (jsonkeeper.com) — combined with the package's otherwise empty functionality — is consistent with a staged or abandoned dropper template rather than a legitimate utility. Routing for human review so a maintainer can assess package legitimacy and watch for activation in subsequent versions.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

7.3.57.3.6

Indicators of compromise (SHA-256)

48e4ad756dbae70bb38049d363961eb27239c7cf18c6a92612579aeb818da7b1

3f6e4b7cef8168fc7a34702dcbb2877618e925d7fca5ca86684a73700d2c7991

80dc74c6c5240e9c146e476300b44582cc114cf1827319ba81d2bcae2d64c2cf

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for environment-gate (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging environment-gate across your stack and pipelines.
If you installed it — respond
Remove environment-gate from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If environment-gate 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 environment-gate 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. environment-gate on npm has been identified as a malicious package (versions 7.3.5, 7.3.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006373GHSA-7h69-vjfv-w92wIN-MAL-2026-008988

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks environment-gate-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database