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

internal-utils-bronxinpm

Advisory published Updated

internal-utils-bronxi is a confirmed malicious npm package (MAL-2025-3132) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 100.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in internal-utils-bronxi (npm)

MAL-2025-3132
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall internal-utils-bronxi

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.

The OpenSSF Package Analysis project identified 'internal-utils-bronxi' @ 100.0.0 (npm) as malicious.

It is considered malicious because:

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

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.0.01.0.1100.0.0

Indicators of compromise (SHA-256)

3b060b166dc77a08c11be2e3aae8d81e5f55f83f1838197b6332c9caf1ed3540
b78d0856150305f5847a1d4e249e801004405aaa6627ae582543ad09fafc8e71
5469955452a077cb8129f89aab2c9c998cc8d693fc2134ffeda8a1edbab643e5
e2c2b247fbdf1610b485929f50b7e3394cf7f7d524a747b5941f0c64563f4407

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for internal-utils-bronxi (3 malicious versions).

  2. If you installed it — respond

    Remove internal-utils-bronxi 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 internal-utils-bronxi 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. internal-utils-bronxi on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 100.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-gvfq-fvj7-q82f

References

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks internal-utils-bronxi-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

internal-utils-bronxi (npm) malicious package — MAL-2025-3132 | O3 Security