Which versions of cat-sis2go-utils are malicious?

The following npm versions of cat-sis2go-utils are flagged malicious: 99.0.0, 99.1.0. Treat any of these as compromised.

How do I remediate cat-sis2go-utils if I installed it?

cat-sis2go-utils 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 cat-sis2go-utils — how do I know if it already compromised me?

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

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

Malicious package

cat-sis2go-utilsnpm

cat-sis2go-utils is a confirmed malicious npm package (MAL-2026-16071) that opens a backdoor for remote access (malicious versions 99.0.0, 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in cat-sis2go-utils (npm)

MAL-2026-16071

Immediate action

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

npm uninstall cat-sis2go-utils

What this malware does

Package [email protected] declares both preinstall and postinstall lifecycle hooks in package.json that execute scripts/run.js on every npm install. The script unconditionally issues a DNS lookup against d22d92dc-84e5-4b58-8cd6-75bf1ac452c7.dnshook.site and POSTs a JSON beacon containing the installer's hostname and process context to https://webhook.site/d22d92dc-84e5-4b58-8cd6-75bf1ac452c7. The package description self-identifies as a dependency-confusion PoC, and the 99.0.0 version is consistent with a resolution-winning squat targeting an internal package name. Installing the package results in arbitrary code execution on the installer host and fingerprints the machine to third-party out-of-band collectors under the operator's control.

Malicious versions

2 flagged

99.0.099.1.0

Indicators of compromise (SHA-256)

205b59e55b3e3474f6b5de7471c11e7095e019a9f1e682083b34eeb7dddd5c3f

ad357542f3dd0e1b598ef36d440b1868ac28c6889226864bf799b2f7b6bf5e91

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

Campaign

IN-MAL-2026-019843IN-MAL-2026-019845

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks cat-sis2go-utils-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