Which versions of set-nested-prop are malicious?

The following npm versions of set-nested-prop are flagged malicious: 2.0.1, 2.0.2. Treat any of these as compromised.

How do I remediate set-nested-prop if I installed it?

set-nested-prop 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 set-nested-prop — how do I know if it already compromised me?

If set-nested-prop 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 set-nested-prop part of a known attack campaign?

Yes — set-nested-prop is associated with the GHSA-r599-4jqx-9665 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 set-nested-prop 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 set-nested-prop (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging set-nested-prop across your stack and pipelines.

Malicious package

set-nested-propnpm

Malicious code in set-nested-prop (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191010

Immediate action

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

npm uninstall set-nested-prop

What this malware does

The package set-nested-prop 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

2.0.12.0.2

Indicators of compromise (SHA-256)

35b0b9a8f67ec13668f93a14f45e037dc7cb3c33fa4c688e13b10a3cd2c5d3a5

1e3ace4ffb79a5de4b7a82ae75ffdcccb6233dce2bfa2a4f32f70a3dc6921a03

3e13f30135c625e03f4fb72e92db400a17819be7d55b3c16d47c12ec33c3cadb

065bce4088a0383e36d16e059774b751a30e4b4ab6035954d1ed2fe553b25402

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

Campaign

GHSA-r599-4jqx-9665

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks set-nested-prop-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