Which versions of unicocheck-ios are malicious?

The following npm versions of unicocheck-ios are flagged malicious: 9.9.9. Treat any of these as compromised.

How do I remediate unicocheck-ios if I installed it?

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

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

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

Malicious package

unicocheck-iosnpm

unicocheck-ios is a confirmed malicious npm package (MAL-2026-5831) that steals credentials and exfiltrates sensitive data (malicious version 9.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in unicocheck-ios (npm)

MAL-2026-5831

Immediate action

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

npm uninstall unicocheck-ios

What this malware does

package.json declares a preinstall lifecycle script that runs curl against https://webhook.site/fe1246c2-ac04-4493-b223-fe34ba26b79f with query parameters carrying the installer's hostname, username ($(whoami)), current working directory, OS uname output, and HOME path. This fires automatically on npm install before any user code runs, leaking host identifiers and environment context to a third-party webhook capture endpoint controlled by the publisher. The package metadata (name unicocheck-ios, description Unico Check iOS SDK - biometric identity verification, version 9.9.9) impersonates the Unico vendor's iOS SDK and uses the canonical dependency-confusion sentinel version, indicating the package is positioned to win resolution against an internal package name and harvest data from build environments that mistakenly fetch it from the public registry.

The OpenSSF Package Analysis project identified 'unicocheck-ios' @ 9.9.9 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

1 flagged

9.9.9

Indicators of compromise (SHA-256)

bafc91c569cf42c5f1ff68531a8d5238919f595368ffa90b7d4e5bcc74fe9788

05ebccc546e1450dad339a76440193233639cd77d9a761ae76f1db67e0e2be7b

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 unicocheck-ios (version 9.9.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging unicocheck-ios across your stack and pipelines.
If you installed it — respond
unicocheck-ios 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 unicocheck-ios 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 unicocheck-ios 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. unicocheck-ios on npm has been identified as a malicious package (version 9.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-006696

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks unicocheck-ios-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