Vulnerability Database · npm · example-backend-next · Version

example-backend-next 0.0.1-security

0.0.1-security is affected by 1 vulnerability.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 1 High 0 Medium 0 Low 0 Unrated 0

Released 16 Mar 2023 Status latest release Also known from other sources 1 Newer releases 1 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

example-backend-next 0.0.1-security vulnerabilities

1 vulnerability cover example-backend-next 0.0.1-security. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Malicious Code Detected in example-backend-next Package N/A critical No fix published 14 Aug 2025

Looking for another version, or everything Vulert holds for example-backend-next?

All versions → Full vulnerability list →

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 →

Questions

About example-backend-next 0.0.1-security

Is example-backend-next 0.0.1-security vulnerable?

Yes. 1 vulnerability in the Vulert database cover example-backend-next 0.0.1-security: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.

Is 0.0.1-security the latest release of example-backend-next?

Yes. 0.0.1-security is the current release, published 16 Mar 2023. Staying on the current line is what keeps you inside the publisher's fixes.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor example-backend-next for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the example-backend-next version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.