Which versions of catqrcodeconverter are malicious?

The following npm versions of catqrcodeconverter are flagged malicious: 99.2.1. Treat any of these as compromised.

How do I remediate catqrcodeconverter if I installed it?

Remove catqrcodeconverter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

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

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

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

Malicious package

catqrcodeconverternpm

catqrcodeconverter is a confirmed malicious npm package (MAL-2026-16435) that executes malicious code on install (malicious version 99.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in catqrcodeconverter (npm)

MAL-2026-16435

Immediate action

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

npm uninstall catqrcodeconverter

What this malware does

Package [email protected] wires both preinstall and postinstall lifecycle hooks in package.json to execute scripts/run.js. On npm install, run.js reads the installer's OS username via os.userInfo() and hostname via os.hostname() and POSTs them as JSON (with the package name) to a hardcoded collector at https://webhook.site/8beeee0f-4dd4-4b25-8588-5a5f83fe6ed2, and issues a DNS canary lookup to 8beeee0f-4dd4-4b25-8588-5a5f83fe6ed2.dnshook.site. The implausibly high version number (99.2.1) is consistent with a dependency-confusion lure intended to win resolution against an internal package name. Installer host identifiers are transmitted to an attacker-controlled endpoint without any user interaction beyond the install command.

Malicious versions

1 flagged

99.2.1

Indicators of compromise (SHA-256)

3333f7b95e551ebf6ed266fb1de661b7419520ed3a922b05910ede132c7d6757

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for catqrcodeconverter (version 99.2.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging catqrcodeconverter across your stack and pipelines.
If you installed it — respond
Remove catqrcodeconverter from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If catqrcodeconverter 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 catqrcodeconverter 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. catqrcodeconverter on npm has been identified as a malicious package (version 99.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020326

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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