Malicious Code Detected in evony-resources-hack173 Package

evony-resources-hack173 Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-20007: Malicious code in evony-resources-hack173 (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 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 evony-resources-hack173 package is an npm package designed to assist users in resource management for the game Evony. It is intended to provide tools and resources to enhance gameplay. However, this package has been identified to contain malicious code, which poses significant risks to users and their systems.

Vulnerability Detail

The vulnerability in the evony-resources-hack173 package stems from the inclusion of malicious code that can compromise user data and system integrity. This code can lead to unauthorized access, data theft, or other harmful actions. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to take immediate action to protect their systems.

How To Fix

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

npm uninstall evony-resources-hack173

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 workaround, users can consider using alternative packages that provide similar functionality without the associated risks. It is advisable to thoroughly review package dependencies and their security status before installation.

Conclusion

The evony-resources-hack173 package has been identified as containing malicious code, posing significant risks to users. Immediate action is required to remove the package and safeguard systems. Users are encouraged to explore alternative packages and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for evony-resources-hack173 →

Share this vulnerability

FAQ

It is an npm package designed for resource management in the game Evony, but it has been found to contain malicious code.

The malicious code can lead to unauthorized access and data theft, posing serious risks to users.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

You should immediately remove the evony-resources-hack173 package from your project to mitigate risks.

Yes, consider using other npm packages that offer similar functionalities without the security risks.

How To Fix

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

npm uninstall evony-resources-hack173

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