# MAL-2026-5743: Malicious code in environment-gate (npm)


- **Type:** Malicious package
- **Package:** `environment-gate` (npm)
- **Published:** 13 Jun 2026
- **Also known as:** GHSA-7h69-vjfv-w92w

## What is MAL-2026-5743?

MAL-2026-5743 is a malicious package in environment-gate, published on 13 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5743?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5743 is a malicious package: environment-gate (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5743/ (Markdown: https://insights.sbomify.com/MAL-2026-5743/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5743

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5743/
Summaries are generated and may contain mistakes; the official description above is the record.