Which versions of undefsafe-typed are malicious?

The following npm versions of undefsafe-typed are flagged malicious: 1.0.3, 1.0.4. Treat any of these as compromised.

How do I remediate undefsafe-typed if I installed it?

undefsafe-typed 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 undefsafe-typed — how do I know if it already compromised me?

If undefsafe-typed 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 undefsafe-typed part of a known attack campaign?

Yes — undefsafe-typed is associated with the GHSA-2xxv-jcwp-f6mp 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 undefsafe-typed 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 undefsafe-typed (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging undefsafe-typed across your stack and pipelines.

Malicious package

undefsafe-typednpm

Malicious code in undefsafe-typed (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190937

Immediate action

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

npm uninstall undefsafe-typed

What this malware does

The package undefsafe-typed 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.31.0.4

Indicators of compromise (SHA-256)

1a19664890dd6d9bba23c333e1095114841ef498dec4eaa02c1bff38bc80aa47

71757e5cdef13d215b8506dfd5b00831fc29a7a24e208472c79fd40c2abe7967

61d1695cc381942c1cb194b90e9d88e7bc0c6b83c5b230e415d42cec0b2e779a

248a30bd302d28f383602d1ba88d5b16d2c91fa4e30c6eda93058df1347de3fa

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

Campaign

GHSA-2xxv-jcwp-f6mp

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks undefsafe-typed-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