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

benmostyn-frame-printnpm

Advisory published Updated

benmostyn-frame-print is a confirmed malicious npm package (MAL-2025-191071) that steals credentials and exfiltrates sensitive data (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in benmostyn-frame-print (npm)

MAL-2025-191071
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall benmostyn-frame-print

What this malware does

The package benmostyn-frame-print 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.0.1

Indicators of compromise (SHA-256)

9ca3536ee7ed6188d6e72988a49a2a0a2a6540c3e1eab0e0fb8c47de44cd1fd9
c88d7f9d2d3efa73dffd3d89701db791d3ce13debeb8a2202de1220e9214441c
e2f0d4b7abe9ddc156e7aa8fd6441240100d81edbc79ad8d29691b1a7f82ab32

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for benmostyn-frame-print (version 1.0.1).

  2. If you installed it — respond

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

Campaign

GHSA-fhmh-4jfp-jcxp

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks benmostyn-frame-print-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

benmostyn-frame-print (npm) malicious package — MAL-2025-191071 | O3 Security