Which versions of @opengov/form-renderer are malicious?

The following npm versions of @opengov/form-renderer are flagged malicious: 0.2.20. Treat any of these as compromised.

How do I remediate @opengov/form-renderer if I installed it?

@opengov/form-renderer 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 @opengov/form-renderer — how do I know if it already compromised me?

If @opengov/form-renderer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @opengov/form-renderer part of a known attack campaign?

Yes — @opengov/form-renderer is associated with the GHSA-j3x7-94xp-wf43 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 @opengov/form-renderer across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @opengov/form-renderer (version 0.2.20).

Malicious package

@opengov/form-renderernpm

Advisory published Mar 26, 2026Updated Apr 7, 2026

@opengov/form-renderer is a confirmed malicious npm package (MAL-2026-2211) that steals credentials and exfiltrates sensitive data (malicious version 0.2.20). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @opengov/form-renderer (npm)

MAL-2026-2211

Immediate action

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

npm uninstall @opengov/form-renderer

What this malware does

The package @opengov/form-renderer 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 CanisterWorm campaign by the TeamPCP threat actor. The malicious payload establishes persistence as user systemd service and places a backdoor on the infected host. The malware will also harvest npm credentials and can autonomously spread.

Malicious versions

1 flagged

0.2.20

Indicators of compromise (SHA-256)

0a1e7a1a86e83336dc53b45347d2f9e12c8861ecd3dbb8b9c8ea9c71d653dc3b

f6c8cb05cb54fe0f2f81f0c9a5ff43f2c4a45ab0fa31bcc1d1cade080e731c3d

a65fcdcab67b898423af17c30461a25301cbcd6a05643565789e361d81d4f9cc

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @opengov/form-renderer (version 0.2.20).
If you installed it — respond
@opengov/form-renderer 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 @opengov/form-renderer was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @opengov/form-renderer on npm has been identified as a malicious package (version 0.2.20 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-j3x7-94xp-wf43

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @opengov/form-renderer-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

Explore

All malware advisories How O3 detects malware Vulnerability database