Which versions of ve-hemi-rewards are malicious?

The following npm versions of ve-hemi-rewards are flagged malicious: 999.0.0. Treat any of these as compromised.

How do I remediate ve-hemi-rewards if I installed it?

ve-hemi-rewards 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 ve-hemi-rewards — how do I know if it already compromised me?

If ve-hemi-rewards 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.

Is ve-hemi-rewards part of a known attack campaign?

Yes — ve-hemi-rewards is associated with the IN-MAL-2026-006483, RLMA-2026-05641, RLUA-2026-06538 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 ve-hemi-rewards across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ve-hemi-rewards (version 999.0.0).

Malicious package

ve-hemi-rewardsnpm

Advisory published Jun 15, 2026Updated Sep 1, 2026

ve-hemi-rewards is a confirmed malicious npm package (MAL-2026-5785) that steals credentials and exfiltrates sensitive data (malicious version 999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ve-hemi-rewards (npm)

MAL-2026-5785

Immediate action

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

npm uninstall ve-hemi-rewards

What this malware does

On npm install, the package's preinstall lifecycle invokes postinstall.js, which collects hostname, username, and current working directory, then iterates process.env and filters keys against the regex /key|secret|token|pass|private|ssh|deploy|auth|api|rpc|wallet|sentry|docker|graph|slack|host/i. The matching key/value pairs (CI tokens, cloud credentials, SSH/deploy keys, RPC and wallet secrets, etc.) are JSON-serialized and POSTed over HTTPS to a hardcoded bare IP, 185.130.46.35:8443/collect. The package name 've-hemi-rewards' at version 999.0.0 with description 'Internal package' is a classic dependency-confusion shape — a high-version stub published to the public registry to override resolution of an organization's private package of the same name. There is no legitimate functionality; the package exists to harvest installer secrets.

Malicious versions

1 flagged

999.0.0

Indicators of compromise (SHA-256)

a8252216c6621e6391775d34f5e32815ab8c2a830df080fed52113b4cf855aa1

57cfe1f9c3f1c9ae54013229ad5cc4e212a840b2ffe4bc9be95f5973128edb41

0ddeabed86dede093c92838eb7178308034943617ce26f5f1247ab3523ac2108

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-006483RLMA-2026-05641RLUA-2026-06538

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks ve-hemi-rewards-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

Explore

All malware advisories How O3 detects malware Vulnerability database