What does the @mypwn/hawkeye malware do?

The OpenSSF Package Analysis project identified '@mypwn/hawkeye' @ 99.0.0 (npm) as malicious. It is considered malicious because: - The package executes one or more commands associated with malicious behavior.

Which versions of @mypwn/hawkeye are malicious?

The following npm versions of @mypwn/hawkeye are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate @mypwn/hawkeye if I installed it?

Remove @mypwn/hawkeye 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.

I already installed @mypwn/hawkeye — how do I know if it already compromised me?

If @mypwn/hawkeye 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.

How do I find @mypwn/hawkeye across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @mypwn/hawkeye (version 99.0.0).

Malicious package

@mypwn/hawkeyenpm

Advisory published Jul 29, 2026Updated Jul 29, 2026

@mypwn/hawkeye is a confirmed malicious npm package (MAL-2026-11157) that executes malicious code on install (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @mypwn/hawkeye (npm)

MAL-2026-11157

Immediate action

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

npm uninstall @mypwn/hawkeye

What this malware does

The OpenSSF Package Analysis project identified '@mypwn/hawkeye' @ 99.0.0 (npm) as malicious.

It is considered malicious because:

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

Malicious versions

1 flagged

99.0.0

Indicators of compromise (SHA-256)

fc7070d4697e41f7bd953772681425e677c8ca9539144154b7abde925adef545

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @mypwn/hawkeye (version 99.0.0).
If you installed it — respond
Remove @mypwn/hawkeye 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.
Did it already run?
If @mypwn/hawkeye 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. @mypwn/hawkeye on npm has been identified as a malicious package (version 99.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @mypwn/hawkeye-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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database