Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

szsec-infos-reportnpm

szsec-infos-report is a confirmed malicious npm package (MAL-2025-66550) that executes malicious code on install (malicious versions 1.0.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in szsec-infos-report (npm)

MAL-2025-66550
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall szsec-infos-report

What this malware does

The package szsec-infos-report was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged
1.0.02.0.1

Indicators of compromise (SHA-256)

4a66d2584bfbfc603ba7d7c07007d21b8a92d63d9ab1a0515088e87c17d40bd4
d0f7d0f83d7810b53b86603e822f34d4b2829f2f0ee8853839340239d99b8388
c921acba5e62eeb63b2f1c088f2ec28e1b9bcfa232357dd76049fcc9a70ae0d5
d8a51627426b3b776cbae863b4a4fd868ffd87195595627928ab03738c0efe82

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for szsec-infos-report (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging szsec-infos-report across your stack and pipelines.

  2. If you installed it — respond

    Remove szsec-infos-report 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.

  3. Did it already run?

    If szsec-infos-report 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.

  4. How O3 protects you

    O3 blocks szsec-infos-report 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. szsec-infos-report on npm has been identified as a malicious package (versions 1.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-qq38-5hjc-c58fRLMA-2025-05955RLUA-2025-06508

References

Credits

  • Amazon Inspector · finder
  • ReversingLabs · finder

Detect & block this

O3 blocks szsec-infos-report-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.

Explore

szsec-infos-report (npm) malicious package — MAL-2025-66550 | O3 Security