Vulnerability Database · npm · baso71 · Version
baso71 1.1.2
1.1.2 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 12 Sep 2024
Status latest release
Licence ISC
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
baso71 1.1.2 vulnerabilities
1 vulnerability cover baso71 1.1.2. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Malicious Code Injection in baso71 Package: A Threat to npm Ecosystem | N/A critical | No fix published | 12 Nov 2025 |
Looking for another version, or everything Vulert holds for baso71?
Questions
About baso71 1.1.2
Is baso71 1.1.2 vulnerable?
Yes. 1 vulnerability in the Vulert database cover baso71 1.1.2: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.1.2 the latest release of baso71?
Yes. 1.1.2 is the current release, published 12 Sep 2024. 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 baso71 for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the baso71 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.