Which versions of m25-transaction-utils are malicious?

The following npm versions of m25-transaction-utils are flagged malicious: 1.1.16. Treat any of these as compromised.

How do I remediate m25-transaction-utils if I installed it?

m25-transaction-utils 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.

I already installed m25-transaction-utils — how do I know if it already compromised me?

If m25-transaction-utils 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.

Is m25-transaction-utils part of a known attack campaign?

Yes — m25-transaction-utils is associated with the GHSA-x328-h4h9-vf2w campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find m25-transaction-utils across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for m25-transaction-utils (version 1.1.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging m25-transaction-utils across your stack and pipelines.

Malicious package

m25-transaction-utilsnpm

Malicious code in m25-transaction-utils (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191127

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall m25-transaction-utils

What this malware does

The package m25-transaction-utils 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

1.1.16

Indicators of compromise (SHA-256)

877baf513fe1e07b3a9c4f2d5f6cb5d6c3fdd62d7f1a13dcb743f45f374e6fbc

4e6e1b5f9279b9960f313db339086c4c955e72e62621d0431c2db33673aad388

5e91218f5eaff53a78f8a4c20f4090ee4c99958d5784c54a3ee2280d00658643

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for m25-transaction-utils (version 1.1.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging m25-transaction-utils across your stack and pipelines.
If you installed it — respond
m25-transaction-utils 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.
Did it already run?
If m25-transaction-utils 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.
How O3 protects you
O3 blocks m25-transaction-utils 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. m25-transaction-utils on npm has been identified as a malicious package (version 1.1.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-x328-h4h9-vf2w

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks m25-transaction-utils-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