Which versions of @tw-marionette/input are malicious?

The following npm versions of @tw-marionette/input are flagged malicious: 99.0.1, 99.0.2, 99.0.4. Treat any of these as compromised.

How do I remediate @tw-marionette/input if I installed it?

Remove @tw-marionette/input from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @tw-marionette/input — how do I know if it already compromised me?

If @tw-marionette/input 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 @tw-marionette/input part of a known attack campaign?

Yes — @tw-marionette/input is associated with the GHSA-584r-4qf7-jqf3 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 @tw-marionette/input 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 @tw-marionette/input (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tw-marionette/input across your stack and pipelines.

Malicious package

@tw-marionette/inputnpm

Malicious code in @tw-marionette/input (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-3071

Immediate action

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

npm uninstall @tw-marionette/input

What this malware does

The package @tw-marionette/input 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.

The OpenSSF Package Analysis project identified '@tw-marionette/input' @ 99.0.1 (npm) as malicious.

It is considered malicious because:

The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged

99.0.199.0.299.0.4

Indicators of compromise (SHA-256)

5064bc6b023c67ddcfdd1f7a4a923c61aa4b1ca6454e97027cd64e049fdbc693

c1061bfd1539c23c74d43f0704fd4939401241d96dbd6516f0a33797ea89a2a2

07b939d5a065e15eeffb61b4cf9311eed3c0198fa431837e730e40fcb02c3f6e

c6b93bf39d5351c220722a3326600c9855309a8e76cb6e10b8cff20f0d9bb102

8c22f8f607175d5c7bf7a5880a8ad93b299d5a219fa75b521749fc2672583765

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @tw-marionette/input (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @tw-marionette/input across your stack and pipelines.
If you installed it — respond
Remove @tw-marionette/input from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @tw-marionette/input 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 @tw-marionette/input 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. @tw-marionette/input on npm has been identified as a malicious package (versions 99.0.1, 99.0.2, 99.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-584r-4qf7-jqf3

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks @tw-marionette/input-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring