NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@ifings/design-systemnpm

Advisory published Updated

@ifings/design-system is a confirmed malicious npm package (MAL-2025-191236) that steals credentials and exfiltrates sensitive data (malicious version 4.9.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @ifings/design-system (npm)

MAL-2025-191236
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @ifings/design-system

What this malware does

The package @ifings/design-system 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged
4.9.2

Indicators of compromise (SHA-256)

dbb1d9f0825ff7f9394d9f62d9b7b65ffc7ba5988590b730c12ece00cec07a28
b08a79c1e782a5cc30405baf5285943e4d9593c937ad998e7353fd2d37ec20d1
c8a2d458b22985eaf37f768018a4359ed4e32182c1c21f0f204e440b8f37772f

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @ifings/design-system (version 4.9.2).

  2. If you installed it — respond

    @ifings/design-system 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.

  3. Did it already run?

    If @ifings/design-system was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @ifings/design-system on npm has been identified as a malicious package (version 4.9.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-3p9v-5g48-hmr6

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @ifings/design-system-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@ifings/design-system (npm) malicious package — MAL-2025-191236 | O3 Security