Which versions of benmostyn-frame-print are malicious?

The following npm versions of benmostyn-frame-print are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate benmostyn-frame-print if I installed it?

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.

I already installed benmostyn-frame-print — how do I know if it already compromised me?

If benmostyn-frame-print 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 benmostyn-frame-print part of a known attack campaign?

Yes — benmostyn-frame-print is associated with the GHSA-fhmh-4jfp-jcxp 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 benmostyn-frame-print 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 benmostyn-frame-print (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging benmostyn-frame-print across your stack and pipelines.

Malicious package

benmostyn-frame-printnpm

Malicious code in benmostyn-frame-print (npm) Remove it immediately and rotate any exposed credentials.

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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for benmostyn-frame-print (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging benmostyn-frame-print across your stack and pipelines.
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.
Did it already run?
If benmostyn-frame-print 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 benmostyn-frame-print 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. 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.

Malware detection Runtime egress monitoring