Which versions of pc-optimizer are malicious?

The following npm versions of pc-optimizer are flagged malicious: 1.0.1, 1.0.2, 1.0.9. Treat any of these as compromised.

How do I remediate pc-optimizer if I installed it?

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

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

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

Malicious package

pc-optimizernpm

pc-optimizer is a confirmed malicious npm package (MAL-2026-5653) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.1, 1.0.2, 1.0.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pc-optimizer (npm)

MAL-2026-5653

Immediate action

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

npm uninstall pc-optimizer

What this malware does

The package's collect.js imports child_process, fs, http, https, and os, reads host identifiers via os.hostname() and os.homedir(), inspects local filesystem paths via fs.existsSync, and POSTs collected data to a hardcoded external endpoint at http://aab.sportsontheweb.net. The destination is not a registry, vendor SDK host, or documented service — it is an unrelated third-party domain bound to a POST in install/load-reachable code. The combination of system enumeration (hostname, homedir, child_process), filesystem inspection, and a hardcoded non-publisher exfiltration endpoint is the canonical host-information stealer fingerprint and provides direct attacker benefit (host fingerprinting + arbitrary collected data shipped off-host).

Malicious versions

3 flagged

1.0.11.0.21.0.9

Indicators of compromise (SHA-256)

9f3f55c554f0b1b48f8ebaa1b8ee6a9d005c972fa06bef7c9727946e5d422aa4

f046d16052b9121c55f2fd5e6eb2be90ce24e7b007efca3c2a9e7f64dab8f6bf

f1dd847960d4aa149ddf901c3b85fa93f3ef2b50d5dfeb64ba3b4599f23ed3aa

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

Campaign

IN-MAL-2026-005748IN-MAL-2026-005750IN-MAL-2026-005749

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks pc-optimizer-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