Which versions of aliftech-ui are malicious?

The following npm versions of aliftech-ui are flagged malicious: 99.9.9. Treat any of these as compromised.

How do I remediate aliftech-ui if I installed it?

aliftech-ui establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed aliftech-ui — how do I know if it already compromised me?

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

Yes — aliftech-ui is associated with the IN-MAL-2026-020508 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 aliftech-ui 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 aliftech-ui (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aliftech-ui across your stack and pipelines.

Malicious package

aliftech-uinpm

aliftech-ui is a confirmed malicious npm package (MAL-2026-17156) that opens a backdoor for remote access (malicious version 99.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in aliftech-ui (npm)

MAL-2026-17156

Immediate action

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

npm uninstall aliftech-ui

What this malware does

postinstall.js runs automatically on npm install and reads os.hostname() and os.userInfo().username, then issues an https.get to a hardcoded webhook.site collector URL (https://webhook.site/539f8bb9-497a-4104-92f7-f95a77204cc2/<hostname>/<username>), embedding the installer identifiers in the URL path. The package name mimics an organization prefix and is published at version 99.9.9, a shape consistent with dependency-confusion targeting of an internal package name; installing it causes any resolving build (including CI) to beacon identifying host and account data to an anonymous third-party collector.

Malicious versions

1 flagged

99.9.9

Indicators of compromise (SHA-256)

e61479316af4cfc0884dfe88744a0ed14fa64e052471cc216667c80502689860

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for aliftech-ui (version 99.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging aliftech-ui across your stack and pipelines.
If you installed it — respond
aliftech-ui establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If aliftech-ui 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 aliftech-ui 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. aliftech-ui on npm has been identified as a malicious package (version 99.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020508

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks aliftech-ui-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database