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

NotifyIconsNuGet

Malicious code in NotifyIcons (NuGet) Remove it immediately and rotate any exposed credentials.

MAL-2024-4572
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
remove NotifyIcons

Malicious versions

123 flagged
1.2.21.2.31.2.41.2.51.2.61.2.71.2.81.2.91.2.101.2.111.2.121.2.131.2.141.2.151.2.161.2.171.2.181.2.191.2.201.2.211.2.221.2.231.2.241.2.251.2.261.2.271.2.281.2.291.2.301.2.311.2.321.2.331.2.341.2.351.2.361.2.371.2.381.2.391.2.401.2.411.2.421.2.431.2.441.2.451.2.461.2.471.2.481.2.491.2.501.2.511.2.521.2.531.2.541.2.551.2.561.2.571.2.581.2.591.2.601.2.611.2.621.2.631.2.641.2.651.2.661.2.671.2.681.2.691.2.701.2.711.2.721.2.731.2.741.2.751.2.761.2.771.2.781.2.791.2.801.2.811.2.821.2.831.2.841.2.851.2.861.2.871.2.881.2.891.2.901.2.911.2.921.2.931.2.941.2.951.2.961.2.971.2.981.2.991.2.1001.2.1011.2.1021.2.1031.2.1041.2.1051.2.1061.2.1071.2.1081.2.1091.2.1101.2.1111.2.1121.2.1131.2.1141.2.1151.2.1161.2.1171.2.1181.2.1191.2.1201.2.1214.6.34.6.44.6.5

Indicators of compromise (SHA-256)

5f1c8569d5c27a4f39dab41c70a081678ea80e0a000b90c742b7a5cd9d4604ae
50fd824f6c6f06a9e0445181e5a920e586613719455d556ca4d44785d942a05a

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 NotifyIcons (123 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging NotifyIcons across your stack and pipelines.

  2. If you installed it — respond

    Remove NotifyIcons 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 NotifyIcons 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 NotifyIcons 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. NotifyIcons on NuGet has been identified as a malicious package (versions 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.2.7, 1.2.8, 1.2.9, and 115 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03364RLUA-2024-07686

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks NotifyIcons-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
NotifyIcons (NuGet) malicious package — MAL-2024-4572 | O3 Security