Which versions of unitel4 are malicious?

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

How do I remediate unitel4 if I installed it?

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

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

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

Yes — unitel4 is associated with the GHSA-hqxg-cjfw-pghj, IN-MAL-2026-017495 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 unitel4 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 unitel4 (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 unitel4 across your stack and pipelines.

Malicious package

unitel4npm

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

MAL-2026-13838

Immediate action

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

npm uninstall unitel4

What this malware does

Package contains only package.json and index.html, with main pointing at index.html. The HTML impersonates a Cloudflare 'Just a moment...' interstitial; its Turnstile callback runs obfuscated JavaScript that constructs a URL ending in a '.club/' domain, appends the current query string, and calls window.location.replace to redirect the browser. There are no preinstall/install/postinstall/prepare lifecycle hooks, and an HTML file cannot be executed via require()/import, so installing or loading this package in a Node.js build environment does not execute the redirect. The payload only fires when the HTML is served to and rendered by an end-user browser, indicating registry abuse to host a phishing/cloaking landing page rather than a supply-chain attack against developers who install 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

1.0.0

Indicators of compromise (SHA-256)

f40dd1ead4de097fb65101b08270f6658934e0281b23cc8f2a6a263bca6afb4f

a5370545a3cd79dd914fd2af5c469caf0f8942c74c14f760f34c3f6856e6648d

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 unitel4 (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 unitel4 across your stack and pipelines.
If you installed it — respond
unitel4 is a typosquat — you almost certainly intended a legitimately-named package. Remove unitel4, 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 unitel4 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 unitel4 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. unitel4 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-hqxg-cjfw-pghjIN-MAL-2026-017495

References

Credits

Amazon Inspector · finder

Detect & block this

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