Which versions of catplatebarcodeparser are malicious?

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

How do I remediate catplatebarcodeparser if I installed it?

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

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

Yes — catplatebarcodeparser is associated with the IN-MAL-2026-020327 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 catplatebarcodeparser 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 catplatebarcodeparser (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 catplatebarcodeparser across your stack and pipelines.

Malicious package

catplatebarcodeparsernpm

catplatebarcodeparser is a confirmed malicious npm package (MAL-2026-16434) 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 catplatebarcodeparser (npm)

MAL-2026-16434

Immediate action

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

npm uninstall catplatebarcodeparser

What this malware does

[email protected] declares preinstall and postinstall lifecycle scripts that execute scripts/run.js on npm install. That script reads os.userInfo().username and os.hostname() and POSTs them to a hardcoded out-of-band collector at https://webhook.site/40e9b065-efd7-43a5-916f-3d52281f42b6, and additionally issues a DNS lookup against 40e9b065-efd7-43a5-916f-3d52281f42b6.dnshook.site as a canary. The version number (99.2.1) and package name pattern are consistent with a dependency-confusion lure intended to win resolution against an internal package of the same name; installing the lure automatically leaks installer identity to an author-controlled endpoint.

Malicious versions

1 flagged

99.2.1

Indicators of compromise (SHA-256)

189a06b0d55d6dab795bcb9ba3a97aa855b2556a54e85e15adc9f5bf20399976

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 catplatebarcodeparser (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 catplatebarcodeparser across your stack and pipelines.
If you installed it — respond
Remove catplatebarcodeparser 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 catplatebarcodeparser 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 catplatebarcodeparser 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. catplatebarcodeparser 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-020327

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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