Which versions of gulp-jscrambler are malicious?

The following npm versions of gulp-jscrambler are flagged malicious: 8.6.2. Treat any of these as compromised.

How do I remediate gulp-jscrambler if I installed it?

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

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

Yes — gulp-jscrambler is associated with the GHSA-2cjx-v4hm-f5gf, IN-MAL-2026-011355 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-jscrambler across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for gulp-jscrambler (version 8.6.2).

Malicious package

gulp-jscramblernpm

Advisory published Jul 15, 2026Updated Aug 5, 2026

gulp-jscrambler is a confirmed malicious npm package (MAL-2026-10673) that steals credentials and exfiltrates sensitive data (malicious version 8.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in gulp-jscrambler (npm)

MAL-2026-10673

Immediate action

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

npm uninstall gulp-jscrambler

What this malware does

gulp-jscrambler is a Gulp plugin wrapping the Jscrambler code-protection API. No install-time lifecycle scripts, credential harvesting, exfiltration endpoints, droppers, or backdoor mechanisms were observed in the package contents. Behavior is consistent with the documented purpose of the package.

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

1 flagged

8.6.2

Indicators of compromise (SHA-256)

d1b1b47b7f27eee6dee1bdd61d3744f11cf323adb9d3d677f13abec5e911007f

c7353f50ebadb90b9c561e3e70b53c89712bafd182fdc3eb16e536651b972092

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for gulp-jscrambler (version 8.6.2).
If you installed it — respond
gulp-jscrambler 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-jscrambler 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. gulp-jscrambler on npm has been identified as a malicious package (version 8.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2cjx-v4hm-f5gfIN-MAL-2026-011355

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks gulp-jscrambler-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