Which versions of @vraksha/gh-helper are malicious?

The following npm versions of @vraksha/gh-helper are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate @vraksha/gh-helper if I installed it?

Remove @vraksha/gh-helper 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 @vraksha/gh-helper — how do I know if it already compromised me?

If @vraksha/gh-helper 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 @vraksha/gh-helper part of a known attack campaign?

Yes — @vraksha/gh-helper is associated with the IN-MAL-2026-008175 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 @vraksha/gh-helper 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 @vraksha/gh-helper (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vraksha/gh-helper across your stack and pipelines.

Malicious package

@vraksha/gh-helpernpm

Malicious code in @vraksha/gh-helper (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-7016

Immediate action

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

npm uninstall @vraksha/gh-helper

What this malware does

On npm install, the package's postinstall hook runs index.js, which performs an HTTPS GET to https://http-logger-production.up.railway.app/payload, base64-decodes the response body (Buffer.from(data.trim(), 'base64').toString('utf-8')), and passes the decoded string to child_process.execSync with { shell: '/bin/bash' }. This is a fetch-decode-exec dropper: the executed content is attacker-controlled, mutable, and opaque, and it runs automatically at install time with the installer's privileges. No legitimate purpose (no shipped native source requiring a build, no vendor-matched SDK, no pinned artifact) justifies this pattern.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

8c867b4c68acc159dea1bbd580c5de3f3c9fef7bd1f54cd48a02c59631ffda12

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @vraksha/gh-helper (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @vraksha/gh-helper across your stack and pipelines.
If you installed it — respond
Remove @vraksha/gh-helper 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 @vraksha/gh-helper 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 @vraksha/gh-helper 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. @vraksha/gh-helper on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-008175

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @vraksha/gh-helper-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