Which versions of @pradhumngautam/common-app are malicious?

The following npm versions of @pradhumngautam/common-app are flagged malicious: 1.0.2. Treat any of these as compromised.

How do I remediate @pradhumngautam/common-app if I installed it?

@pradhumngautam/common-app 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 @pradhumngautam/common-app — how do I know if it already compromised me?

If @pradhumngautam/common-app 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 @pradhumngautam/common-app part of a known attack campaign?

Yes — @pradhumngautam/common-app is associated with the GHSA-cxhj-8vrg-j895 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 @pradhumngautam/common-app across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @pradhumngautam/common-app (version 1.0.2).

Malicious package

@pradhumngautam/common-appnpm

Advisory published Nov 24, 2025Updated Dec 1, 2025

@pradhumngautam/common-app is a confirmed malicious npm package (MAL-2025-191048) that steals credentials and exfiltrates sensitive data (malicious version 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @pradhumngautam/common-app (npm)

MAL-2025-191048

Immediate action

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

npm uninstall @pradhumngautam/common-app

What this malware does

The package @pradhumngautam/common-app was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.2

Indicators of compromise (SHA-256)

36ee90617c75cd14cb7ec33cdad1ede590325c86c06cb5f5f7b89f7e397a698a

73b8f4984f6f466e9c4815fda8c4b2d9cd182bc0fd8435aa53e25c2ad3c46b29

8984d278847eccce8a7e440093a12e26681f10e6534f163544592f20e7539c81

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @pradhumngautam/common-app (version 1.0.2).
If you installed it — respond
@pradhumngautam/common-app 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 @pradhumngautam/common-app 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. @pradhumngautam/common-app 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.

Campaign

GHSA-cxhj-8vrg-j895

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @pradhumngautam/common-app-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