Which versions of meta-templates are malicious?

The following npm versions of meta-templates are flagged malicious: 1.0.0, 1.0.1, 1.0.2. Treat any of these as compromised.

How do I remediate meta-templates if I installed it?

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

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

Yes — meta-templates is associated with the RLMA-2026-05157, RLUA-2026-06325 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 meta-templates across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for meta-templates (3 malicious versions).

Malicious package

meta-templatesnpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

meta-templates is a confirmed malicious npm package (MAL-2026-7319) that executes malicious code on install (malicious versions 1.0.0, 1.0.1, 1.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in meta-templates (npm)

MAL-2026-7319

Immediate action

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

npm uninstall meta-templates

Malicious versions

3 flagged

1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

ff88d660dc773753ed7aa5a33ca94e4256602af6deeb7820783a9593f6c8e00e

42fec0ab48183467b40eba37983b3621fbbddfe788c9a7b0118aa23ba70bf234

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for meta-templates (3 malicious versions).
If you installed it — respond
Remove meta-templates 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 meta-templates 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. meta-templates on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-05157RLUA-2026-06325

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks meta-templates-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

Explore

All malware advisories How O3 detects malware Vulnerability database