Malicious Code Detected in deno-r4-basic Package - Security Alert

deno-r4-basic Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6713: Malicious code in deno-r4-basic (npm). Affects deno-r4-basic versions >= 1.1.0. 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 deno-r4-basic package is an npm library designed for basic Deno functionalities. It is utilized by developers to streamline their Deno applications. However, this package has been identified as having a vulnerability that allows it to communicate with a domain linked to malicious activities, posing a significant risk to users and their applications.

Vulnerability Detail

The vulnerability in the deno-r4-basic package originates from its ability to connect to a domain associated with malicious activities. This can lead to unauthorized data access, potential data breaches, and exploitation of the affected systems. The issue was introduced in version 1.1.0, making it critical for users to be aware of the risks involved with using this package.

How To Fix

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

npm uninstall deno-r4-basic

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 workaround, users can avoid using the deno-r4-basic package until a secure version is released. Alternatively, consider using other libraries that provide similar functionalities without the associated risks.

Conclusion

The deno-r4-basic package has a significant vulnerability that allows it to connect to a malicious domain, posing risks to users. It is crucial to update to the latest version or find alternative solutions to ensure the security of your applications.

See every vulnerability recorded for deno-r4-basic →

Share this vulnerability

FAQ

The deno-r4-basic package is an npm library that provides basic functionalities for Deno applications.

The package communicates with a domain linked to malicious activities, which can lead to unauthorized access and data breaches.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without needing to sign up.

As a temporary measure, avoid using the deno-r4-basic package until a secure version is available or consider using alternative libraries.

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

How To Fix

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

npm uninstall deno-r4-basic

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