MAL-2026-14488
Vulnerability from ossf_malicious_packages – Published: 2026-08-25 08:34 – Updated: 2026-08-25 08:34 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
python-walletlibr-v
|
0.7.9
|
python-walletlibr-v is a wallet-lookalike PyPI package that ships no wallet functionality — only a stub hello() that prints 'Hello from my custom library!' and placeholder author metadata (author = 'Your Name'). Its setup.py registers a CustomInstall command that, on Windows at pip install time, writes a.bat file into %TEMP%, spawns a new cmd.exe console to execute it via subprocess.Popen(['cmd.exe','/k', bat_path], CREATE_NEW_CONSOLE), and calls os.system('calc'). Arbitrary local command execution fires automatically during pip install on Windows hosts, unrelated to any advertised functionality.
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
setup.py
|
sha256
d0b7ed3487fb76de391846693737f7cd9b1a385d967854c5ca111ea2c06f5126tlsh
6f2120028977097516b1036b0916cc06ffaea4a35775b28636fc4e349fba021060e93f |
| Evidence file |
pycryptoshuffle/__init__.py
|
sha256
a9eed37934c714a36a35e6adea50014e0fad2d323d1628b1d8e4a92bbaa2c134tlsh
25c09b450657155191dcc47f5500691179fd40b03fd55015573c311e79571555de524c |
| Package archive |
python_walletlibr_v-0.7.9.tar.gz
|
blake2b_256
caf2051e75361d70d22f00732f27905e1223cb70ba0be6c6f831f8f191384905md5
16935464ca0bc132b702dccd08a04b5asha256
7450765e50d74a4aed668e4159b58fa1b82a5d709bb6376fec84ed4776ecc6a5 |
- CWE-506 - Embedded Malicious Code
| URL | Tags |
|---|---|
| https://pypi.org/project/python-walletlibr-v/0.7.9/ | PACKAGE |
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "setup.py",
"sha256": "d0b7ed3487fb76de391846693737f7cd9b1a385d967854c5ca111ea2c06f5126",
"tlsh": "6f2120028977097516b1036b0916cc06ffaea4a35775b28636fc4e349fba021060e93f"
},
{
"path": "pycryptoshuffle/__init__.py",
"sha256": "a9eed37934c714a36a35e6adea50014e0fad2d323d1628b1d8e4a92bbaa2c134",
"tlsh": "25c09b450657155191dcc47f5500691179fd40b03fd55015573c311e79571555de524c"
}
],
"package_integrity": [
{
"filename": "python_walletlibr_v-0.7.9.tar.gz",
"hashes": {
"blake2b_256": "caf2051e75361d70d22f00732f27905e1223cb70ba0be6c6f831f8f191384905",
"md5": "16935464ca0bc132b702dccd08a04b5a",
"sha256": "7450765e50d74a4aed668e4159b58fa1b82a5d709bb6376fec84ed4776ecc6a5"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "python-walletlibr-v"
},
"versions": [
"0.7.9"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-018733",
"import_time": "2026-08-25T08:49:18.077188637Z",
"modified_time": "2026-08-25T08:34:01Z",
"sha256": "6783cffec9c8f9377babacd1cb4490a278bace564b34861bf49b35258be7220c",
"source": "amazon-inspector",
"versions": [
"0.7.9"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (6783cffec9c8f9377babacd1cb4490a278bace564b34861bf49b35258be7220c)\npython-walletlibr-v is a wallet-lookalike PyPI package that ships no wallet functionality \u2014 only a stub hello() that prints \u0027Hello from my custom library!\u0027 and placeholder author metadata (__author__ = \u0027Your Name\u0027). Its setup.py registers a CustomInstall command that, on Windows at pip install time, writes a.bat file into %TEMP%, spawns a new cmd.exe console to execute it via subprocess.Popen([\u0027cmd.exe\u0027,\u0027/k\u0027, bat_path], CREATE_NEW_CONSOLE), and calls os.system(\u0027calc\u0027). Arbitrary local command execution fires automatically during pip install on Windows hosts, unrelated to any advertised functionality.\n",
"id": "MAL-2026-14488",
"modified": "2026-08-25T08:34:01Z",
"published": "2026-08-25T08:34:01Z",
"references": [
{
"type": "PACKAGE",
"url": "https://pypi.org/project/python-walletlibr-v/0.7.9/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in python-walletlibr-v (PyPI)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.