RUSTSEC-2023-0110 json
`postgresderive` was removed from crates.io for malicious code
published 3y ago modified 7mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
This crate was part of a typosquatting malware cluster published by the malicious user `amaperf` and contained a malware payload in `build.rs` to exfiltrate host information to the attacker.
This advisory is to retrospectively document this attempted attack. The version information and download records of the malicious crate are no longer available. The related malicious crates have been yanked, and the malicious account has been banned.
Thanks to Louis Lang at [Phylum] (now [Veracode]) for reporting this malware campaign.
[Phylum]: https://phylum.io/ [Veracode]: https://www.veracode.com/
Is RUSTSEC-2023-0110 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | postgresderive | >=0.0.0-0 |
no fix listed |
References
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.