Which versions of mon-package-react-typescript are malicious?

The following npm versions of mon-package-react-typescript are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate mon-package-react-typescript if I installed it?

mon-package-react-typescript 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 mon-package-react-typescript — how do I know if it already compromised me?

If mon-package-react-typescript 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 mon-package-react-typescript part of a known attack campaign?

Yes — mon-package-react-typescript is associated with the GHSA-m6gj-2fm9-896j 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 mon-package-react-typescript 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 mon-package-react-typescript (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging mon-package-react-typescript across your stack and pipelines.

Malicious package

mon-package-react-typescriptnpm

Malicious code in mon-package-react-typescript (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190976

Immediate action

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

npm uninstall mon-package-react-typescript

What this malware does

The package mon-package-react-typescript 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.1

Indicators of compromise (SHA-256)

b461712e072f1d4ded3cbb5f004683c386e5d60ac6c04d84714a13d671ec6798

22b741df148115219cefc4a7110caf4494a1b84698a1ffa9609550097e8f4894

ba342197c7eaf5f0742b334dedebd7634ef19d42a378bcb9ce3656fd2d5a8a27

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

Campaign

GHSA-m6gj-2fm9-896j

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks mon-package-react-typescript-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