Malicious Code Detected in askama Package - Security Alert

askama Updated 02 Oct 2025

Summary

23/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6276: Malicious code in askama (npm). Affects askama versions >= 0.12.1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The askama package is a templating engine for Rust, designed to facilitate the creation of HTML templates. It is widely used in web development for its efficiency and ease of integration. However, recent findings have revealed that certain versions of this package communicate with a domain linked to malicious activities, posing a significant security risk to applications that utilize it.

Vulnerability Detail

The vulnerability in the askama package arises from its communication with a domain associated with malicious activities. This behavior can lead to unauthorized data access, potential data breaches, and exploitation of the affected applications. The issue was introduced in version 0.12.1, and it is crucial for developers to be aware of the implications of using this compromised version.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall askama

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, you can avoid using the affected version of the askama package by downgrading to a previous stable version that does not exhibit this malicious behavior. Use the command: npm install askama@<previous_version>, replacing <previous_version> with a version number prior to 0.12.1.

Conclusion

The discovery of malicious code in the askama package highlights the importance of maintaining up-to-date dependencies in software development. Developers should take immediate action to update or downgrade the package to mitigate potential security risks.

See every vulnerability recorded for askama →

Share this vulnerability

FAQ

Askama is a templating engine for Rust that allows developers to create HTML templates easily and efficiently.

The vulnerability involves the package communicating with a domain linked to malicious activities, which can compromise application security.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

Consider downgrading to a previous stable version of the askama package until you can apply the necessary updates.

The vulnerability was identified by Amazon Inspector, a security service that helps identify vulnerabilities in applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall askama

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback