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

@acme-types/acme-packagenpm

Advisory published Updated

@acme-types/acme-package is a confirmed malicious npm package (MAL-2025-48954) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @acme-types/acme-package (npm)

MAL-2025-48954
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @acme-types/acme-package

What this malware does

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 installs a dependency hosted on a custom domain that runs an info stealer during installation. The info stealer focuses on stealing npm, git, and other CI/CD related tokens.

Malicious versions

1 flagged
99.0.0

Indicators of compromise (SHA-256)

f1b754e0118dde98a24e6f1ea46eb2ed30d7b59cd938fbc627e6dc4429251482
d2f857f12a85ce5ac1b726195f454c150a111e0ff809dbf9b2688c0177cb85c2
d35200732b0308cdd7088ed7e6031318fd8407c8c4cdda27a68e86efa80e4fa7

Detection & response playbook

Credential / info stealer

  1. Find it

    Search your lockfiles and build artifacts for @acme-types/acme-package (version 99.0.0).

  2. If you installed it — respond

    @acme-types/acme-package 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 @acme-types/acme-package 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. @acme-types/acme-package on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hjhm-4vmv-wm8xRLMA-2025-05646

References

Credits

  • ReversingLabs · finder

Detect & block this

O3 blocks @acme-types/acme-package-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
@acme-types/acme-package (npm) malicious package — MAL-2025-48954 | O3 Security