Which versions of gifuct are malicious?

The following npm versions of gifuct are flagged malicious: 2.1.2. Treat any of these as compromised.

How do I remediate gifuct if I installed it?

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

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

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

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

Malicious package

gifuctnpm

Malicious code in gifuct (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-10451

Immediate action

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

npm uninstall gifuct

What this malware does

Package name typosquats the legitimate gifuct-js GIF parser and re-exports it as cover. On module load, code reconstructs the host filament-zap.vercel.app and paths /service/assets/fetchBinary / /service/assets/fetchLinuxBinary from String.fromCharCode numeric arrays, downloads a platform-specific executable, writes it to a WinMetrics/WinService.exe path under the user data directory, chmods it 0755 on Linux, and spawns it detached with stdio ignored and unref'd. The payload is fetched over an obfuscated, unpinned URL with no hash or signature verification, and the download-and-execute path is unrelated to the advertised GIF-parsing purpose.

Malicious versions

1 flagged

2.1.2

Indicators of compromise (SHA-256)

965f65127a6b6d2a6865e91efe6a878ae1e076b9ef4de23152aef4ee6080038b

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

Campaign

IN-MAL-2026-010259

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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