Which versions of valid-south-african-id are malicious?

The following npm versions of valid-south-african-id are flagged malicious: 1.0.3. Treat any of these as compromised.

How do I remediate valid-south-african-id if I installed it?

valid-south-african-id 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 valid-south-african-id — how do I know if it already compromised me?

If valid-south-african-id 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 valid-south-african-id part of a known attack campaign?

Yes — valid-south-african-id is associated with the GHSA-pw36-3phc-xfph 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 valid-south-african-id 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 valid-south-african-id (version 1.0.3). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging valid-south-african-id across your stack and pipelines.

Malicious package

valid-south-african-idnpm

Malicious code in valid-south-african-id (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190942

Immediate action

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

npm uninstall valid-south-african-id

What this malware does

The package valid-south-african-id 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.3

Indicators of compromise (SHA-256)

c9659b9cbce833f3dcd45a355bdcd56df7841ea2fbafce0b4959defc7c406b47

7a363caeeaaa83a715f0d38b64608e11a39a272a42abe53c92dbbacb133dc927

389753a519a766e6f2002b7c7b7c7e58a057653bb076e95eefff5ec82e021fa7

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

Campaign

GHSA-pw36-3phc-xfph

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks valid-south-african-id-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