Which versions of gulp-inject-envs are malicious?

The following npm versions of gulp-inject-envs are flagged malicious: 1.2.1, 1.2.2. Treat any of these as compromised.

How do I remediate gulp-inject-envs if I installed it?

gulp-inject-envs 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 gulp-inject-envs — how do I know if it already compromised me?

If gulp-inject-envs 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 gulp-inject-envs part of a known attack campaign?

Yes — gulp-inject-envs is associated with the GHSA-f74h-jm63-v9h3 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 gulp-inject-envs 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 gulp-inject-envs (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gulp-inject-envs across your stack and pipelines.

Malicious package

gulp-inject-envsnpm

Malicious code in gulp-inject-envs (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191105

Immediate action

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

npm uninstall gulp-inject-envs

What this malware does

The package gulp-inject-envs was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged

1.2.11.2.2

Indicators of compromise (SHA-256)

5dafa09839ea07c586670ac1a302805fb65ffaf32d1641dcab2be569a68231f3

76e39a64762012ce36fceca1accb200c9452fb8150739c1d31ed72789a75a7bd

d230a528331dc71aa1fa5cb1d9fd8146d79d7e92f3aae2efd2ce7c177640b337

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

Campaign

GHSA-f74h-jm63-v9h3

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gulp-inject-envs-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