Which versions of hifromhere1 are malicious?

The following npm versions of hifromhere1 are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate hifromhere1 if I installed it?

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

If hifromhere1 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 hifromhere1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for hifromhere1 (version 1.0.2).

Malicious package

hifromhere1npm

Advisory published Apr 20, 2026Updated Apr 23, 2026

hifromhere1 is a confirmed malicious npm package (MAL-2026-2951) that executes malicious code on install (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in hifromhere1 (npm)

MAL-2026-2951

Immediate action

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

npm uninstall hifromhere1

What this malware does

The package hifromhere1 was found to contain malicious code.

The OpenSSF Package Analysis project identified 'hifromhere1' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

f3892fddb7ae9153b581282718ffa15c76fb58da83d1976acda33cd1ba93718f

82931dc7313b2b9b93b8664655cbe445702e0fdcf1cc7e587b27758d2ef9cda1

Detection & response playbook

Malicious package

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

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks hifromhere1-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