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

@citi-icg-158830/icgds-react-cssnpm

Malicious code in @citi-icg-158830/icgds-react-css (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3808
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @citi-icg-158830/icgds-react-css

What this malware does

The package @citi-icg-158830/icgds-react-css 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.

The OpenSSF Package Analysis project identified '@citi-icg-158830/icgds-react-css' @ 0.0.0-defensive-callback.1 (npm) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
0.0.0-defensive-callback.1

Indicators of compromise (SHA-256)

c5837600ff9a7d2e50ab5baef9d4de8b77ff7628fe085381b5ee90d1c317f421
6255b5d27ddf97d5093328983d54e39a05ce73176cdc472aa2df8499fa506f1e
fec4517e764cd179c4ea0d70772e55e6468537c79765222ee4c87336197696b1

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 @citi-icg-158830/icgds-react-css (version 0.0.0-defensive-callback.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @citi-icg-158830/icgds-react-css across your stack and pipelines.

  2. If you installed it — respond

    Remove @citi-icg-158830/icgds-react-css 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 @citi-icg-158830/icgds-react-css 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 @citi-icg-158830/icgds-react-css 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. @citi-icg-158830/icgds-react-css on npm has been identified as a malicious package (version 0.0.0-defensive-callback.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-729h-2x9h-56v4

References

Credits

  • Amazon Inspector · finder
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @citi-icg-158830/icgds-react-css-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.