Which versions of jinja-template are malicious?

Every published version of jinja-template on npm is considered malicious. Remove the package entirely.

How do I remediate jinja-template if I installed it?

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

If jinja-template 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 jinja-template part of a known attack campaign?

Yes — jinja-template is associated with the GHSA-42gx-7w4g-27q2 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 jinja-template 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 jinja-template (all published versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jinja-template across your stack and pipelines.

Malicious package

jinja-templatenpm

Malicious code in jinja-template (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-1352

Immediate action

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

npm uninstall jinja-template

What this malware does

The package jinja-template 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

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

777241a05ff1b9cafa5358e6127f852378179af0ed1c2c6c1ccea769cd94b398

6e79b3bda068fff4a0d32858209d995e311925bda047742e96a1c4bd5424083a

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

Campaign

GHSA-42gx-7w4g-27q2

References

github.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks jinja-template-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