Which versions of react-context-form-tdsss are malicious?

The following npm versions of react-context-form-tdsss are flagged malicious: 9.0.0. Treat any of these as compromised.

How do I remediate react-context-form-tdsss if I installed it?

react-context-form-tdsss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed react-context-form-tdsss — how do I know if it already compromised me?

If react-context-form-tdsss 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 react-context-form-tdsss part of a known attack campaign?

Yes — react-context-form-tdsss is associated with the IN-MAL-2026-007596 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 react-context-form-tdsss 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 react-context-form-tdsss (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-context-form-tdsss across your stack and pipelines.

Malicious package

react-context-form-tdsssnpm

Malicious code in react-context-form-tdsss (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6512

Immediate action

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

npm uninstall react-context-form-tdsss

What this malware does

[email protected] is a dependency-confusion payload. package.json declares scripts.preinstall="node index.js", and index.js issues an HTTPS GET to a hardcoded interactsh/OAST subdomain (d8v0o1a9io6mjndcpbgghpfmkcgcm6dno.oast.online/npm-installed) on install. This beacon discloses the installer's public IP and confirms code execution on the installer's host to the operator of the OAST listener. The package.json description self-identifies as a dependency-confusion PoC and declares a self-dependency, the shape used to squat an internal/private package name on the public registry so that resolution in a victim environment pulls and executes this code. Installing this package causes outbound network beaconing on the installer's machine without consent.

The OpenSSF Package Analysis project identified 'react-context-form-tdsss' @ 9.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

9.0.0

Indicators of compromise (SHA-256)

7a53e75a65681ee9ea818634ddee1ed52c6c8398dbd68e2b6abca255b24aaf37

93a527c5b8a2dec60d70994e1423e4138bdc1a6218cf11ff7528919767b3dea3

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for react-context-form-tdsss (version 9.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging react-context-form-tdsss across your stack and pipelines.
If you installed it — respond
react-context-form-tdsss establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If react-context-form-tdsss 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 react-context-form-tdsss 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. react-context-form-tdsss on npm has been identified as a malicious package (version 9.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007596

References

npmjs.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks react-context-form-tdsss-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring