Which versions of dhjksficgwu2 are malicious?

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

How do I remediate dhjksficgwu2 if I installed it?

dhjksficgwu2 is a typosquat — you almost certainly intended a legitimately-named package. Remove dhjksficgwu2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed dhjksficgwu2 — how do I know if it already compromised me?

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

Yes — dhjksficgwu2 is associated with the GHSA-f4wq-4wgj-f595, IN-MAL-2026-017528 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 dhjksficgwu2 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 dhjksficgwu2 (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 dhjksficgwu2 across your stack and pipelines.

Malicious package

dhjksficgwu2npm

dhjksficgwu2 is a confirmed malicious npm package (MAL-2026-13802) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in dhjksficgwu2 (npm)

MAL-2026-13802

Immediate action

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

npm uninstall dhjksficgwu2

What this malware does

Package contains a single index.html file declared as main. The HTML impersonates a Cloudflare Turnstile 'Just a moment...' verification page (sitekey 0x4AAAAAADrvn4rDM7WVvgPh) and includes an inline script that reconstructs a redirect target from an obfuscated string array (_0x522c) plus URL query parameters, then assigns window.location to that URL. There is no package.json lifecycle script, no JavaScript main, and no code that runs when the package is installed or required in Node; requiring an HTML file is a no-op. The artifact appears to be phishing/redirect content hosted on npm rather than code that attacks developers who install it.

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)

a7437cbf09fc5c0da0b7f3fff5ba28904f46e534acc257790a054d6fe132bfdb

f5dc64d0022ee36cd898963db50e3c835990bf94837821fb34408820855c69c0

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for dhjksficgwu2 (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 dhjksficgwu2 across your stack and pipelines.
If you installed it — respond
dhjksficgwu2 is a typosquat — you almost certainly intended a legitimately-named package. Remove dhjksficgwu2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If dhjksficgwu2 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 dhjksficgwu2 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. dhjksficgwu2 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-f4wq-4wgj-f595IN-MAL-2026-017528

References

Credits

Amazon Inspector · finder

Detect & block this

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