Which versions of prompt-eng are malicious?

The following npm versions of prompt-eng are flagged malicious: 1.0.50. Treat any of these as compromised.

How do I remediate prompt-eng if I installed it?

prompt-eng 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 prompt-eng — how do I know if it already compromised me?

If prompt-eng 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 prompt-eng part of a known attack campaign?

Yes — prompt-eng is associated with the GHSA-hjww-r2g4-w9fh 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 prompt-eng 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 prompt-eng (version 1.0.50). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prompt-eng across your stack and pipelines.

Malicious package

prompt-engnpm

Malicious code in prompt-eng (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190988

Immediate action

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

npm uninstall prompt-eng

What this malware does

The package prompt-eng 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.50

Indicators of compromise (SHA-256)

d083c02cac026e95833622ff25f63998d1bf9eab18133d01efb0db5907a605f5

35ffadd9d8117a0735b89706cf5f82bd6ea30cf8e51c826efa41364bab2c362f

6cc2449e894a467556d3e8eed95646bca94c39f5a93c342acb15d9aec5623e3e

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 prompt-eng (version 1.0.50). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging prompt-eng across your stack and pipelines.
If you installed it — respond
prompt-eng 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 prompt-eng 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 prompt-eng 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. prompt-eng on npm has been identified as a malicious package (version 1.0.50 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hjww-r2g4-w9fh

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks prompt-eng-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