Malicious Code Detected in awkkoans Package - Security Alert

awkkoans Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-15221: Malicious code in awkkoans (npm). Affected versions are not published. 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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The awkkoans package is an npm library designed for educational purposes, allowing users to learn JavaScript through interactive coding challenges. While it serves as a valuable resource for developers, its recent discovery of malicious code poses a significant security risk, potentially compromising user systems and data.

Vulnerability Detail

The awkkoans package has been identified to contain malicious code that could lead to unauthorized access or manipulation of user data. This vulnerability originated from the package's codebase, which was compromised, allowing attackers to inject harmful scripts. Users of this package are at risk of data breaches, system instability, and other security threats due to this malicious code.

How To Fix

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

npm uninstall awkkoans

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, users can avoid using the awkkoans package and seek alternative educational resources or libraries that do not pose security risks. Additionally, ensure that your project dependencies are regularly monitored for vulnerabilities.

Conclusion

The discovery of malicious code in the awkkoans package highlights the importance of vigilance when using open-source libraries. Users are advised to remove the package and monitor their dependencies for vulnerabilities to ensure the security of their applications.

See every vulnerability recorded for awkkoans →

Share this vulnerability

FAQ

The awkkoans package is an npm library designed to help users learn JavaScript through interactive coding challenges.

The malicious code found in awkkoans could potentially allow unauthorized access to user data and compromise system security.

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.

If you have used the awkkoans package, it is crucial to uninstall it immediately and replace it with a safer alternative.

Yes, there are many alternatives available, such as freeCodeCamp, Codecademy, and various other JavaScript learning resources that do not pose security risks.

How To Fix

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

npm uninstall awkkoans

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