Which versions of jexkcode are malicious?

The following npm versions of jexkcode are flagged malicious: 1.0.1, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4. Treat any of these as compromised.

How do I remediate jexkcode if I installed it?

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

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

Yes — jexkcode is associated with the GHSA-j72h-3h5h-43v5 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 jexkcode across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for jexkcode (6 malicious versions).

Malicious package

jexkcodenpm

Advisory published Sep 16, 2026Updated Sep 30, 2026

jexkcode is a confirmed malicious npm package (MAL-2026-16220) that executes malicious code on install (malicious versions 1.0.1, 1.1.0, 1.1.1…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in jexkcode (npm)

MAL-2026-16220

Immediate action

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

npm uninstall jexkcode

What this malware does

Versions 1.0.1 through 1.1.4 of jexkcode automatically follow a hard-coded WhatsApp newsletter whenever a WhatsApp connection opens. The package waits three seconds and calls newsletterFollow without obtaining user consent or exposing a configuration option. The README advertises newsletter support but does not disclose this automatic account modification. Versions through 1.1.1 used a malformed newsletter JID; version 1.1.2 corrected it. Subsequent commits removed both failure and success logs, so version 1.1.4 performs the automatic follow without visible output. This behavior is unrelated to the package's stated functionality and modifies the user's WhatsApp account without authorization.

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

6 flagged

1.0.11.1.01.1.11.1.21.1.31.1.4

Indicators of compromise (SHA-256)

8f980863fb53dc94d2a73765b57ce8f4224675d722d63f3a9381eb8044415072

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for jexkcode (6 malicious versions).
If you installed it — respond
Remove jexkcode 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 jexkcode 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. jexkcode on npm has been identified as a malicious package (versions 1.0.1, 1.1.0, 1.1.1, 1.1.2, 1.1.3, 1.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j72h-3h5h-43v5

References

Credits

smiling-hyena · finder

Detect & block this

O3 blocks jexkcode-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