Which versions of cjdfswifuem3 are malicious?

The following npm versions of cjdfswifuem3 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate cjdfswifuem3 if I installed it?

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

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

Yes — cjdfswifuem3 is associated with the GHSA-w32m-789q-9hgh, IN-MAL-2026-017541 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 cjdfswifuem3 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 cjdfswifuem3 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cjdfswifuem3 across your stack and pipelines.

Malicious package

cjdfswifuem3npm

cjdfswifuem3 is a confirmed malicious npm package (MAL-2026-13793) 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 cjdfswifuem3 (npm)

MAL-2026-13793

Immediate action

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

npm uninstall cjdfswifuem3

What this malware does

The package has no JavaScript module; package.json declares main as index.html, which cannot be require()'d, so installing or importing this package produces no code execution on the installer. The sole shipped content is an index.html that renders a fake 'Performing security verification' page impersonating a Cloudflare Turnstile challenge, then after ~1s executes obfuscator.io-style code (rotating string array _0x5d5d, base64 decoder _0x92a0 with self-defense anti-debug class, indirect accessors) that constructs a URL and calls window.location.replace(targetUrl.toString()), forwarding the visitor's query parameters to a destination that is not readable in the shipped source. The only in-clear URLs are decoy cloudflare.com footer links used to sell the disguise. The npm registry is being abused as a hosting/distribution channel for a phishing-lure page rather than as a code package. Installers who run npm install cjdfswifuem3 are not attacked (no lifecycle scripts, no importable code, no credential access); the victims are end users who reach the hosted HTML via a phishing link. This is registry abuse warranting takedown but is not an installer-side supply-chain attack under this engine's threat model.

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

1.0.0

Indicators of compromise (SHA-256)

732b38878101a7d2632168e8014abfd9b8cf68f5625601bc05a2604cee9c5ff9

565ffd2f5127412df02a03f80345ff2420dc5545b65abff5298eac3bf1bf2990

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 cjdfswifuem3 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging cjdfswifuem3 across your stack and pipelines.
If you installed it — respond
cjdfswifuem3 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 cjdfswifuem3 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 cjdfswifuem3 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. cjdfswifuem3 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

GHSA-w32m-789q-9hghIN-MAL-2026-017541

References

Credits

Amazon Inspector · finder

Detect & block this

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