Which versions of forms-new-design are malicious?

The following npm versions of forms-new-design are flagged malicious: 1.0.0, 99.99.9. Treat any of these as compromised.

How do I remediate forms-new-design if I installed it?

Remove forms-new-design 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 forms-new-design — how do I know if it already compromised me?

If forms-new-design 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 forms-new-design part of a known attack campaign?

Yes — forms-new-design is associated with the GHSA-x7cr-x9qx-f6j4, RLMA-2026-01325 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 forms-new-design 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 forms-new-design (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging forms-new-design across your stack and pipelines.

Malicious package

forms-new-designnpm

Malicious code in forms-new-design (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-286

Immediate action

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

npm uninstall forms-new-design

What this malware does

The package forms-new-design 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.

Malicious versions

2 flagged

1.0.099.99.9

Indicators of compromise (SHA-256)

9cf1f5f8d78c6e26b45ef4a895859922f68ff7afb558284111a34f497681b324

45f98af63ec853b571da818f8d974890156b0fd52c9c2ab3fa74a4e213ff3f0a

76e8e2897d92a21e281a31ee9bbca2b3899861cb3a79628afce21951f19cd5b3

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

Campaign

GHSA-x7cr-x9qx-f6j4RLMA-2026-01325

References

github.com

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks forms-new-design-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