Which versions of tfjs-custom-module are malicious?

The following npm versions of tfjs-custom-module are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate tfjs-custom-module if I installed it?

tfjs-custom-module 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 tfjs-custom-module — how do I know if it already compromised me?

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

Yes — tfjs-custom-module is associated with the IN-MAL-2026-018278 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 tfjs-custom-module across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for tfjs-custom-module (version 1.0.0).

Malicious package

tfjs-custom-modulenpm

tfjs-custom-module is a confirmed malicious npm package (MAL-2026-14196) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in tfjs-custom-module (npm)

MAL-2026-14196

Immediate action

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

npm uninstall tfjs-custom-module

What this malware does

tfjs-custom-module is a typosquat of the tensorflow/tfjs package. Its package.json declares a postinstall lifecycle script that runs automatically on npm install. The script collects installer host identifiers — os.hostname(), process.platform, process.arch, process.version, package name, and the npm lifecycle event — and POSTs them as JSON via https.request to the hardcoded external host 8xq4kw5d.instances.poc.jchunt.top at path /tfjs-custom-module. The endpoint is not the installer's infrastructure and the beacon is not opt-in. This is host-reconnaissance exfiltration to an author-controlled destination running under a look-alike canary domain, regardless of any self-labeling as security research.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

c50d87a4593cb5a0444f2333f368180b64dfb5d3b8f37e0baf4f6d686ea2ef74

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-018278

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks tfjs-custom-module-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