Which versions of sa-company-registration-number-regex are malicious?

The following npm versions of sa-company-registration-number-regex are flagged malicious: 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate sa-company-registration-number-regex if I installed it?

sa-company-registration-number-regex 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 sa-company-registration-number-regex — how do I know if it already compromised me?

If sa-company-registration-number-regex 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 sa-company-registration-number-regex part of a known attack campaign?

Yes — sa-company-registration-number-regex is associated with the GHSA-wmrc-wxq7-xfh7 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 sa-company-registration-number-regex 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 sa-company-registration-number-regex (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging sa-company-registration-number-regex across your stack and pipelines.

Malicious package

sa-company-registration-number-regexnpm

Malicious code in sa-company-registration-number-regex (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191008

Immediate action

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

npm uninstall sa-company-registration-number-regex

What this malware does

The package sa-company-registration-number-regex 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

2 flagged

1.0.11.0.2

Indicators of compromise (SHA-256)

7f96cef751cbb400c6ab56ec32a9ecbc68444b2429b6267c1bcb285647cc33d4

f15485422c9807206afeb3c43ed1e03d2f2499b0c689d8bf253e663cf72d7fa7

d5ba52bdaefe4bd5f7ba06b567380c1d4c8081bceb3d91f89061227ac95a8f4f

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

Campaign

GHSA-wmrc-wxq7-xfh7

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks sa-company-registration-number-regex-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